From: Greg KH <gregkh@linuxfoundation.org>
To: Thomas Deutschmann <whissi@gentoo.org>
Cc: Eddie Chapman <eddie@ehuk.net>,
stable@vger.kernel.org, davem@davemloft.net,
nicolas.dichtel@6wind.com, netdev@vger.kernel.org
Subject: Re: Request for stable 4.14.x inclusion: net: don't call update_pmtu unconditionally
Date: Tue, 1 May 2018 08:04:11 -0700 [thread overview]
Message-ID: <20180501150411.GG14123@kroah.com> (raw)
In-Reply-To: <1ae8845f-6106-29e1-ceec-02eff35beed9@gentoo.org>
On Tue, May 01, 2018 at 12:15:37AM +0200, Thomas Deutschmann wrote:
> Hi,
>
> On 2018-04-30 20:22, Greg KH wrote:
> > The geneve hunk doesn't apply at all to the 4.14.y tree, so I think
> > someone has a messed up tree somewhere...
> >
> > I'll go look into this now.
>
> Mh?
>
> > $ git clone https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
> > $ cd linux-stable
> > $ git checkout v4.14.38
> > $ git cherry-pick 52a589d51f1008f62569bf89e95b26221ee76690
>
> Works for me... then I cherry-pick
> f15ca723c1ebe6c1a06bc95fda6b62cd87b44559 on top, adjust
> "net/ipv6/ip6_tunnel.c" like shown in my previous mail and everything is
> fine for me...
Ah crap, I missed the dependancy here as well, it was a long day
yesterday...
I'll drop this and try it again for the next release.
greg k-h
prev parent reply other threads:[~2018-05-01 15:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-22 21:50 Request for stable 4.14.x inclusion: net: don't call update_pmtu unconditionally Thomas Deutschmann
2018-04-27 12:20 ` Thomas Deutschmann
2018-04-27 13:51 ` Greg KH
2018-04-27 14:39 ` David Miller
2018-04-27 14:45 ` Greg KH
2018-04-27 16:04 ` Eddie Chapman
2018-04-27 18:07 ` Thomas Deutschmann
2018-04-27 18:43 ` Eddie Chapman
2018-04-28 4:41 ` Greg KH
2018-04-30 18:22 ` Greg KH
2018-04-30 22:15 ` Thomas Deutschmann
2018-05-01 15:04 ` 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=20180501150411.GG14123@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=davem@davemloft.net \
--cc=eddie@ehuk.net \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=stable@vger.kernel.org \
--cc=whissi@gentoo.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.