From: Greg KH <gregkh@linuxfoundation.org>
To: Patrick Schaaf <netdev@bof.de>
Cc: <netdev@vger.kernel.org>, Yuval Mintz <Yuval.Mintz@qlogic.com>
Subject: Re: [PATCH] [BACKPORT] [3.14.56] bnx2x: Don't notify about scratchpad parities
Date: Tue, 01 Mar 2016 06:25:45 +0000 [thread overview]
Message-ID: <20160301062544.GG3200@kroah.com> (raw)
In-Reply-To: <1686003.8SMzEu8fpg@rofl>
On Thu, Dec 10, 2015 at 02:37:34PM +0100, Patrick Schaaf wrote:
> On Friday 06 November 2015 09:32:46 Greg KH wrote:
> > On Thu, Nov 05, 2015 at 11:18:37AM +0100, Patrick Schaaf wrote:
> > > bnx2x: Don't notify about scratchpad parities
> > >
> > > This is a (trivial) "backport" of ad6afbe9578d1fa26680faf78c846bd8c00d1d6e
> > > to stable kernel 3.14.56.
> >
> > This patch isn't in 4.1 either, do you want it there as well?
>
> Hi Greg,
>
> I didn't see the patch in 3.14.57 or 3.14.58 - could you please consider it
> again (for all stable kernels that don't have it)?
>
> My three machines with bnx2x interfaces have been running file with patch
> 3.14.56, for the last 35 days. The original problematic event (spewing a
> million messages which are suppressed by that patch), did not reoccur so far
> (neither did any other issue, dmesg is completely empty since boot).
>
> best regards
> Patrick
>
> Related earlier posts / reports, for reference:
>
> http://marc.info/?l=linux-netdev&m=144663711626469
> http://lists.openwall.net/netdev/2015/11/05/48
Sorry for the long delay, now queued up.
greg k-h
prev parent reply other threads:[~2016-03-01 6:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 10:18 [PATCH] [BACKPORT] [3.14.56] bnx2x: Don't notify about scratchpad parities Patrick Schaaf
2015-11-06 17:32 ` Greg KH
2015-11-06 17:40 ` Patrick Schaaf
2015-12-10 13:37 ` Patrick Schaaf
2016-03-01 6:25 ` Greg KH [this message]
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=20160301062544.GG3200@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Yuval.Mintz@qlogic.com \
--cc=netdev@bof.de \
--cc=netdev@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).