From: Ben Hutchings <ben@decadent.org.uk>
To: Greg KH <greg@kroah.com>
Cc: Ajit Khaparde <ajitk@serverengines.com>,
netdev <netdev@vger.kernel.org>,
stable-review@kernel.org, David Miller <davem@davemloft.net>,
stable@kernel.org
Subject: Re: [stable] [PATCH] be2net: Bug fix to support newer generation of BE ASIC
Date: Thu, 28 Jan 2010 23:55:56 +0000 [thread overview]
Message-ID: <1264722956.373.561.camel@localhost> (raw)
In-Reply-To: <20100128232829.GA31884@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 1113 bytes --]
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@kernel.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.
Ben.
--
Ben Hutchings
You can't have everything. Where would you put it?
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2010-01-28 23:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 7:56 [PATCH] be2net: Bug fix to support newer generation of BE ASIC Ajit Khaparde
2010-01-28 22:40 ` Ben Hutchings
2010-01-28 22:51 ` [stable] " Greg KH
2010-01-28 23:20 ` Ben Hutchings
2010-01-28 23:28 ` Greg KH
2010-01-28 23:55 ` Ben Hutchings [this message]
2010-01-29 5:51 ` Ajit Khaparde
2010-01-29 5:56 ` David Miller
2010-01-29 6:47 ` Ajit Khaparde
2010-01-29 7:05 ` David Miller
2010-01-29 7:03 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1264722956.373.561.camel@localhost \
--to=ben@decadent.org.uk \
--cc=ajitk@serverengines.com \
--cc=davem@davemloft.net \
--cc=greg@kroah.com \
--cc=netdev@vger.kernel.org \
--cc=stable-review@kernel.org \
--cc=stable@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.