From: Greg KH <gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public•gmane.org>
To: Anoob Soman <anoob.soman-Sxgqhf6Nn4DQT0dZR+AlfA@public•gmane.org>
Cc: dev-yBygre7rU0TnMu66kgdUjQ@public•gmane.org,
Eric Dumazet
<eric.dumazet-Re5JQEeQqe8AvxtiuMwx3w@public•gmane.org>,
netdev-u79uwXL29TY76Z2rM5mHXA@public•gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public•gmane.org,
stable-u79uwXL29TY76Z2rM5mHXA@public•gmane.org,
davem-fT/PcQaiUtIeIZ0/mPfg9Q@public•gmane.org
Subject: Re: [PATCH 4.4-only] openvswitch: clear sender cpu before forwarding packets
Date: Thu, 18 May 2017 10:11:49 +0200 [thread overview]
Message-ID: <20170518081149.GA31512@kroah.com> (raw)
In-Reply-To: <371bcd34-10fa-867f-8bfb-7f61caf11cbe-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org>
On Wed, May 17, 2017 at 10:21:09AM +0100, Anoob Soman wrote:
> On 17/05/17 09:19, Greg KH wrote:
> > Why is this a non-upstream patch? What commit in Linus's tree fixed
> > this? Why not just backport that?
> >
> > thanks,
> >
> > greg k-h
>
> Agreed, I think it is sensible to backport 52bd2d62ce67 "net: better
> skb->sender_cpu and skb->napi_id cohabitation" to 4.4, rather than having a
> different patch.
So backporting that one patch solves the issue here? Can you please
verify it, and let me know before I apply it?
thanks,
greg k-h
next prev parent reply other threads:[~2017-05-18 8:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 14:25 [PATCH 4.4-only] openvswitch: clear sender cpu before forwarding packets Anoob Soman
2017-05-16 19:55 ` Joe Stringer
[not found] ` <1494944710-7901-1-git-send-email-anoob.soman-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org>
2017-05-17 8:19 ` Greg KH
2017-05-17 9:21 ` Anoob Soman
[not found] ` <371bcd34-10fa-867f-8bfb-7f61caf11cbe-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org>
2017-05-18 8:11 ` Greg KH [this message]
2017-05-19 10:28 ` Anoob Soman
2017-05-21 8:47 ` kbuild test robot
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=20170518081149.GA31512@kroah.com \
--to=gregkh-hqyy1w1ycw8ekmwlsbkhg0b+6bgklq7r@public$(echo .)gmane.org \
--cc=anoob.soman-Sxgqhf6Nn4DQT0dZR+AlfA@public$(echo .)gmane.org \
--cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public$(echo .)gmane.org \
--cc=dev-yBygre7rU0TnMu66kgdUjQ@public$(echo .)gmane.org \
--cc=eric.dumazet-Re5JQEeQqe8AvxtiuMwx3w@public$(echo .)gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
--cc=stable-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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