From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
torvalds@linux-foundation.org, stable@vger.kernel.org,
lwn@lwn.net, jslaby@suse.cz
Subject: Re: Linux 4.14.297
Date: Tue, 8 Nov 2022 09:12:37 +0100 [thread overview]
Message-ID: <Y2oPdQVmMDWCTZ8q@kroah.com> (raw)
In-Reply-To: <CAKwvOdk378tUkqXzS8_NvWZRfayQjJAtJX81PdemuBVZ16i4Dg@mail.gmail.com>
On Mon, Nov 07, 2022 at 10:38:51AM -0800, Nick Desaulniers wrote:
> On Sat, Nov 5, 2022 at 2:57 AM Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > On Fri, Nov 04, 2022 at 11:17:45AM -0700, Nick Desaulniers wrote:
> > > On Tue, Nov 01, 2022 at 07:24:13PM +0100, Greg Kroah-Hartman wrote:
> > > > I'm announcing the release of the 4.14.297 kernel.
> > > >
> > > > All users of the 4.14 kernel series must upgrade.
> > > >
> > > > The updated 4.14.y git tree can be found at:
> > > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.14.y
> > > > and can be browsed at the normal kernel.org git web browser:
> > > > https://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary
> > >
> > > Hi Greg and stable tree maintainers,
> > > Please consider cherry-picking
> > > commit 95b980d62d52 ("linux/bits.h: make BIT(), GENMASK(), and friends available in assembly")
> > > back to 4.19.y and 4.14.y. It first landed in v5.3-rc1 and applies
> > > cleanly to both branches. I did not find any fixups to 95b980d62d52,
> > > FWIW.
> > >
> > > Otherwise users upgrading to this point release of linux-4.14.y still on
> > > versions of the GNU assembler older than v1.28 will observe assembler
> > > errors when building this series. See the link below for the error
> > > messages.
> > >
> > > Please see
> > > https://lore.kernel.org/llvm/20221103210748.1343090-1-ndesaulniers@google.com/
> > > for more info.
> >
> > Did you try building with that commit applied? I get the following
>
> I built 4.19 but not 4.14. Sorry! It looks like for 4.14 95b980d62d52
> will additionally depend on
>
> commit 2dd8a62c6476 ("linux/const.h: move UL() macro to include/linux/const.h")
>
> which first landed in v4.17-rc1.
>
> That commit will depend on
>
> commit 2a6cc8a6c0cb ("linux/const.h: prefix include guard of
> uapi/linux/const.h with _UAPI")
>
> which first landed in v4.17-rc1 as well. Looks like they were part of
> the same series.
>
> So 4.14.y will need the following 3 patches:
> 1. commit 2a6cc8a6c0cb ("linux/const.h: prefix include guard of
> uapi/linux/const.h with _UAPI")
> 2. commit 2dd8a62c6476 ("linux/const.h: move UL() macro to
> include/linux/const.h")
> 3. commit 95b980d62d52 ("linux/bits.h: make BIT(), GENMASK(), and
> friends available in assembly")
>
> 2a6cc8a6c0cb will have a minor conflict in include/uapi/linux/const.h because
> commit a85cbe6159ff ("uapi: move constants from <linux/kernel.h> to
> <linux/const.h>")
> was backported before 2a6cc8a6c0cb as b732e14e6218b (in 4.14).
> Attached is a compile tested (x86 make CC=clang) mbox for 4.14.y.
> Please let me know if that works for you.
Thanks, I've queued these up now and will test them later today on the
Android build system as well.
greg k-h
prev parent reply other threads:[~2022-11-08 8:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 18:24 Linux 4.14.297 Greg Kroah-Hartman
2022-11-01 18:24 ` Greg Kroah-Hartman
2022-11-04 18:17 ` Nick Desaulniers
2022-11-05 9:57 ` Greg Kroah-Hartman
2022-11-07 18:38 ` Nick Desaulniers
2022-11-08 8:12 ` 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=Y2oPdQVmMDWCTZ8q@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=ndesaulniers@google.com \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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).