Date: Wed, 6 Mar 2013 07:01:31 +0000 From: "Duvvuru,Venkat Kumar" <VenkatKumar.Duvvuru@Emulex.Com> To: Josh Paetzel <josh@tcbug.org> Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Subject: RE: OCE driver patches Message-ID: <BF3270C86E8B1349A26C34E4EC1C44CB215D9B59@CMEXMB1.ad.emulex.com> In-Reply-To: <E59FC35E-9111-4667-B0D7-0D716C2F4DF8@tcbug.org> References: <BF3270C86E8B1349A26C34E4EC1C44CB215A0220@CMEXMB1.ad.emulex.com> <B3A73C45-3299-4EDD-BE38-9D027E9D548A@tcbug.org> <BF3270C86E8B1349A26C34E4EC1C44CB215D84F9@CMEXMB1.ad.emulex.com> <E59FC35E-9111-4667-B0D7-0D716C2F4DF8@tcbug.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--_002_BF3270C86E8B1349A26C34E4EC1C44CB215D9B59CMEXMB1ademulex_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Josh, I'm attaching a .tgz file of the patches (oce0.patch to oce24.patch, Please= make sure that you apply them in the same order) that I told you about for= the Emulex's OCE driver. I had opened a PR for the same, However .tgz files are not allowed as attac= hments to the problem report, So I just renamed .tgz file to .txt for uploa= ding. However I have not gotten any email notification on that problem report, co= uld be because of the attachment problem I guess.=20 Please let me know if I could open a PR without any attachment and send you= that PR number. Also there is a notification about freebsd 8.4 code freeze by March 8. It = would be nice if we could get these patches in before the code freeze on 8.= 4 as well. Pls suggest. Thanks, Venkat. -----Original Message----- From: Josh Paetzel [mailto:josh@tcbug.org]=20 Sent: Friday, March 01, 2013 8:08 PM To: Duvvuru,Venkat Kumar Cc: freebsd-net@freebsd.org Subject: Re: OCE driver patches On Mar 1, 2013, at 5:36 AM, "Duvvuru,Venkat Kumar" <VenkatKumar.Duvvuru@Emu= lex.Com> wrote: > Hi Josh, > I have a bunch of patches (~25 in number) to submit. Please let me know t= he process to submit them. > Do I just attach them in a single email or open pr's for each of them?? > Pls suggest. >=20 > /Venkat >=20 Venkat, I think it depends on how you want them committed to FreeBSD.=20 If the patches are atomic changes that should be kept atomic in the FreeBSD= source tree then I'll commit them seperately. This is a tad time consuming= as I test them atomically before committing them. If they can be committe= d in one go then I can just apply them all, test the end result, and commit= that. One PR with the patches attached and a note saying these can all go in in o= ne go is appropriate in the latter case, the former would be best served by= seperate PRs. Thanks, Josh Paetzel --_002_BF3270C86E8B1349A26C34E4EC1C44CB215D9B59CMEXMB1ademulex_--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BF3270C86E8B1349A26C34E4EC1C44CB215D9B59>