netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Greg KH <gregkh@suse.de>
Cc: "Skidmore, Donald C" <donald.c.skidmore@intel.com>,
	"stable@kernel.org" <stable@kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH] ixgbe: fix for 82599 erratum on Header Splitting
Date: Sat, 05 Mar 2011 00:06:05 -0800	[thread overview]
Message-ID: <1299312365.26413.35.camel@jtkirshe-MOBL1> (raw)
In-Reply-To: <20110305075926.GA19706@suse.de>

[-- Attachment #1: Type: text/plain, Size: 2043 bytes --]

On Fri, 2011-03-04 at 23:59 -0800, Greg KH wrote:
> On Fri, Mar 04, 2011 at 11:51:07PM -0800, Jeff Kirsher wrote:
> > On Fri, 2011-03-04 at 23:44 -0800, Greg KH wrote:
> > > On Fri, Mar 04, 2011 at 11:06:07PM -0800, Jeff Kirsher wrote:
> > > > From: Don Skidmore <donald.c.skidmore@intel.com>
> > > > 
> > > > We have found a hardware erratum on 82599 hardware that can lead to
> > > > unpredictable behavior when Header Splitting mode is enabled.  So
> > > > we are no longer enabling this feature on affected hardware.
> > > > 
> > > > Signed-off-by: Don Skidmore <donald.c.skidmore@intel.com>
> > > > Tested-by: Stephen Ko <stephen.s.ko@intel.com>
> > > > Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
> > > > ---
> > > >  drivers/net/ixgbe/ixgbe_main.c |    4 ++++
> > > 
> > > I'm confused, why did you just send this patch to me?
> > > 
> > > What am I supposed to do with it?
> > > 
> > > greg k-h
> > 
> > This is the fix for ixgbe (that Ben and others pointed out) which has
> > been accepted into Linus's tree which did not apply to stable-2.6.32
> > tree.  This is the updated patch that apply's to the stable-2.6.32 tree.
> 
> How nice, but why didn't you say so in the first place?  Am I really
> supposed to remember the hundreds of stable patches I handle every week?

Sorry, I sent you/stable an email saying that I would send you an
updated patch that would apply to stable-2.6.32.  I know you deal with a
number of patches, so I apologize.

> 
> Oh, I need the git commit id of it as well, care to resend this with
> that and the proper "please apply this for the .32 longterm tree"
> message so I can?
> 

Heres is the commit info:
commit a124339ad28389093ed15eca990d39c51c5736cc
Author: Don Skidmore <donald.c.skidmore@intel.com>
Date:   Tue Jan 18 22:53:47 2011 +0000


> If so, I'll queue it up for the after-next .32-longterm release.
> 

I can resend the entire patch submission again, with the info provided,
if necessary.

> thanks,
> 
> greg k-h



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

      reply	other threads:[~2011-03-05  8:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-05  7:06 [PATCH] ixgbe: fix for 82599 erratum on Header Splitting Jeff Kirsher
2011-03-05  7:44 ` Greg KH
2011-03-05  7:51   ` Jeff Kirsher
2011-03-05  7:59     ` Greg KH
2011-03-05  8:06       ` Jeff Kirsher [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=1299312365.26413.35.camel@jtkirshe-MOBL1 \
    --to=jeffrey.t.kirsher@intel.com \
    --cc=donald.c.skidmore@intel.com \
    --cc=gregkh@suse.de \
    --cc=netdev@vger.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 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).