[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100129055157.GA10427@serverengines.com>
Date: Fri, 29 Jan 2010 11:21:59 +0530
From: Ajit Khaparde <ajitkhaparde@...il.com>
To: Ben Hutchings <ben@...adent.org.uk>
Cc: Greg KH <greg@...ah.com>, netdev <netdev@...r.kernel.org>,
stable-review@...nel.org, David Miller <davem@...emloft.net>,
stable@...nel.org
Subject: Re: [stable] [PATCH] be2net: Bug fix to support newer generation
of BE ASIC
On 28/01/10 23:55 +0000, Ben Hutchings wrote:
> On Thu, 2010-01-28 at 15:28 -0800, Greg KH wrote:
> > On Thu, Jan 28, 2010 at 11:20:28PM +0000, Ben Hutchings wrote:
> > > On Thu, 2010-01-28 at 14:51 -0800, Greg KH wrote:
> > > > On Thu, Jan 28, 2010 at 10:40:29PM +0000, Ben Hutchings wrote:
> > > [...]
> > > > > Also, you should either send this patch to stable@...nel.org, or NAK the
> > > > > addition of PCI ids for BladeEngine 3 in 2.6.32.7.
> > > >
> > > > Why? How does the pci id patch for 2.6.32.7 matter with this change?
> > >
> > > Because it looks like the devices being added won't work without this.
> >
> > Hm, what is "this"? I seem to have been lost on this thread.
>
> The patch I was replying to
> <http://article.gmane.org/gmane.linux.network/150441> changes I/O setup
> for be2net to use PCI BAR 0 on the new device whereas it uses BAR 1 on
> older devices.
>
> > Care to explain it better? 2.6.32.7 is now out with the pci ids, so if
> > I need to add something else for the next .32-stable kernel, please let
> > me know.
>
> Well that will be for Ajit to sort out.
My apologies for the confusion.
I was out of action for almost a month. As I got back few days back,
I noticed that the patch to include the new PCI IDs was pushed to
the stable kernel. So, I gathered the changes necessary for supporting the
new generation of ASIC, that were made in my absence and spun this patch.
When I mailed the patch, I was not sure when to CC stable@...nel.org
We would like to have the PCI Ids for BladeEngine 3 in 2.6.32 kernel.
Dave,
I plan rectify the error pointed by Ben and Greg and spin the patch again and
resend it. Please let me know if you think otherwise.
Thanks
Ajit
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists