From: Kees Cook <keescook@chromium.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: linux-stable <stable@vger.kernel.org>,
lkft-triage@lists.linaro.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sasha Levin <sashal@kernel.org>,
Anders Roxell <anders.roxell@linaro.org>,
linux-hardening@vger.kernel.org,
Palmer Dabbelt <palmer@rivosinc.com>
Subject: Re: stable-rc: 6.1: gcc-plugins: Reorganize gimple includes for GCC 13
Date: Thu, 10 Aug 2023 20:30:52 -0700 [thread overview]
Message-ID: <202308102030.76B5309D1@keescook> (raw)
In-Reply-To: <CA+G9fYugggRyxJFgxRwb0GvgXPerCE928S5vVW7ZnzfTJCRnZA@mail.gmail.com>
On Fri, Aug 11, 2023 at 08:47:53AM +0530, Naresh Kamboju wrote:
> > > # first fixed commit: [e6a71160cc145e18ab45195abf89884112e02dfb]
> > > gcc-plugins: Reorganize gimple includes for GCC 13
> [...]
>
> > Commit e6a71160cc14 ("gcc-plugins: Reorganize gimple includes
> > for GCC 13") was added in v6.2.
>
> This commit is needed.
>
> >
> > I think you're saying you need it backported to the v6.1 stable tree?
> > ("First bad commit" is really the first good commit?)
>
> First good commit.
> We need to backport this patch for linux.6.1.y
Okay! Thanks. :) Yeah, this could probably go to all the stable kernels,
if someone wants to build with GCC 13 on older kernels.
--
Kees Cook
next prev parent reply other threads:[~2023-08-11 3:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 5:27 stable-rc: 6.1: gcc-plugins: Reorganize gimple includes for GCC 13 Naresh Kamboju
2023-08-10 20:31 ` Kees Cook
2023-08-11 3:17 ` Naresh Kamboju
2023-08-11 3:30 ` Kees Cook [this message]
2023-08-11 3:34 ` Palmer Dabbelt
2023-08-11 6:27 ` Greg Kroah-Hartman
2023-08-11 14:18 ` Greg Kroah-Hartman
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=202308102030.76B5309D1@keescook \
--to=keescook@chromium.org \
--cc=anders.roxell@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-hardening@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=palmer@rivosinc.com \
--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