From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nathan Chancellor <natechancellor@gmail.com>
Cc: stable@vger.kernel.org
Subject: Re: Apply 2ae89c7a82ea to all active branches
Date: Thu, 7 Jun 2018 21:54:04 +0200 [thread overview]
Message-ID: <20180607195404.GA3024@kroah.com> (raw)
In-Reply-To: <20180607192434.GA3373@localhost>
On Thu, Jun 07, 2018 at 12:24:34PM -0700, Nathan Chancellor wrote:
> Hi Greg,
>
> Please apply 2ae89c7a82ea ("kconfig: Avoid format overflow warning from
> GCC 8.1") to all active branches. I am rather tired of seeing these
> warnings every time I need to compile. It will apply cleanly.
Normally, as this is properly tagged for a stable tree, it will get
automatically added after it is in a -rc release. But as that's a few
weeks away, I'll take it now, thanks for letting me know.
greg k-h
prev parent reply other threads:[~2018-06-07 19:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-07 19:24 Apply 2ae89c7a82ea to all active branches Nathan Chancellor
2018-06-07 19:54 ` Greg Kroah-Hartman [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=20180607195404.GA3024@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=natechancellor@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).