From: Greg KH <greg@kroah.com>
To: Ben Hutchings <ben@decadent.org.uk>
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 14:51:14 -0800 [thread overview]
Message-ID: <20100128225114.GA1588@kroah.com> (raw)
In-Reply-To: <1264718429.373.520.camel@localhost>
On Thu, Jan 28, 2010 at 10:40:29PM +0000, Ben Hutchings wrote:
> On Thu, 2010-01-28 at 13:26 +0530, Ajit Khaparde wrote:
> > Bug fix in be2net for newer generation of BladeEngine ASIC.
> [...]
> > @@ -2162,6 +2168,7 @@ static int be_stats_init(struct be_adapter *adapter)
> > cmd->va = pci_alloc_consistent(adapter->pdev, cmd->size, &cmd->dma);
> > if (cmd->va == NULL)
> > return -1;
> > + memset(cmd->va, cmd->size, 0);
Heh, that's funny. Yeah, that is not correct at all. If that does
anything, something else is seriously wrong :)
> > return 0;
> > }
> >
> [...]
>
> I don't think this does what you think it does.
>
> 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?
confused,
greg k-h
next prev parent reply other threads:[~2010-01-28 22:52 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 ` Greg KH [this message]
2010-01-28 23:20 ` [stable] " Ben Hutchings
2010-01-28 23:28 ` Greg KH
2010-01-28 23:55 ` Ben Hutchings
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=20100128225114.GA1588@kroah.com \
--to=greg@kroah.com \
--cc=ajitk@serverengines.com \
--cc=ben@decadent.org.uk \
--cc=davem@davemloft.net \
--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.