public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Julian Wiedmann <jwi@linux.ibm.com>
Cc: Sasha Levin <sashal@kernel.org>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	"David S . Miller" <davem@davemloft.net>,
	linux-s390@vger.kernel.org
Subject: Re: [PATCH AUTOSEL 4.19 204/205] s390/qeth: limit csum offload erratum to L3 devices
Date: Fri, 8 Nov 2019 13:34:16 +0100	[thread overview]
Message-ID: <20191108123416.GA732985@kroah.com> (raw)
In-Reply-To: <4d8f1938-af6e-7e0e-4085-2f7c53390b2d@linux.ibm.com>

On Fri, Nov 08, 2019 at 01:16:26PM +0100, Julian Wiedmann wrote:
> On 08.11.19 13:00, Sasha Levin wrote:
> > On Fri, Nov 08, 2019 at 12:50:24PM +0100, Julian Wiedmann wrote:
> >> On 08.11.19 12:37, Sasha Levin wrote:
> >>> From: Julian Wiedmann <jwi@linux.ibm.com>
> >>>
> >>> [ Upstream commit f231dc9dbd789b0f98a15941e3cebedb4ad72ad5 ]
> >>>
> >>> Combined L3+L4 csum offload is only required for some L3 HW. So for
> >>> L2 devices, don't offload the IP header csum calculation.
> >>>
> >>
> >> NACK, this has no relevance for stable.
> > 
> > Sure, I'll drop it.
> > 
> > Do you have an idea why the centos and ubuntu folks might have
> > backported this commit into their kernels?
> > 
> 
> No clue, I trust they have their own reasons.
> 

I cant see centos backporting anything unless they were asked to do so.
And this really looks like a "bugfix" to me, why isn't this relevant for
any older kernel versions?

thanks,

greg k-h

  reply	other threads:[~2019-11-08 12:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191108113752.12502-1-sashal@kernel.org>
2019-11-08 11:37 ` [PATCH AUTOSEL 4.19 204/205] s390/qeth: limit csum offload erratum to L3 devices Sasha Levin
2019-11-08 11:50   ` Julian Wiedmann
2019-11-08 12:00     ` Sasha Levin
2019-11-08 12:16       ` Julian Wiedmann
2019-11-08 12:34         ` Greg KH [this message]
2019-11-08 19:35           ` David Miller
2019-11-11  7:17             ` Julian Wiedmann

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=20191108123416.GA732985@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=davem@davemloft.net \
    --cc=jwi@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=sashal@kernel.org \
    --cc=stable@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