[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <DM2PR11MB0124541010FE79CFA0CA8CC993860@DM2PR11MB0124.namprd11.prod.outlook.com>
Date: Mon, 28 Mar 2016 12:09:58 +0000
From: Manish Chopra <manish.chopra@...gic.com>
To: David Miller <davem@...emloft.net>
CC: netdev <netdev@...r.kernel.org>,
Dept-GE Linux NIC Dev <Dept-GELinuxNICDev@...gic.com>,
Harish Patil <harish.patil@...gic.com>
Subject: RE: [PATCH net-next 1/1] qlge: Update version to 1.00.00.35
> -----Original Message-----
> From: David Miller [mailto:davem@...emloft.net]
> Sent: Friday, March 25, 2016 9:12 PM
> To: Manish Chopra <manish.chopra@...gic.com>
> Cc: netdev <netdev@...r.kernel.org>; Dept-GE Linux NIC Dev <Dept-
> GELinuxNICDev@...gic.com>; Harish Patil <harish.patil@...gic.com>
> Subject: Re: [PATCH net-next 1/1] qlge: Update version to 1.00.00.35
>
> From: Manish Chopra <manish.chopra@...gic.com>
> Date: Fri, 25 Mar 2016 07:14:09 -0400
>
> > Just updating version as many fixes got accumulated over 1.00.00.34
> >
> > Signed-off-by: Manish Chopra <manish.chopra@...gic.com>
>
> Applied, but it is the 'net' tree that fixes et al. like this should be targetting as
> 'net-next' is closed.
Thanks Dave. By the way I used to see an announcement regarding "net-next is CLOSED" on netdev which I don't see these days.
I know that there are other ways to know this but I think it's much easier and straight to know this from announcement email so that
everybody be more aware of NOT sending patches for net-next over this period at first place.
Powered by blists - more mailing lists