From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
Christoph Hellwig <hch@lst.de>,
Russell King <rmk+kernel@armlinux.org.uk>,
Sasha Levin <sashal@kernel.org>,
linux-stable <stable@vger.kernel.org>
Subject: Re: ARM: 9109/1: oabi-compat: add epoll_pwait handler
Date: Thu, 16 Sep 2021 10:41:05 +0200 [thread overview]
Message-ID: <YUMDIUe7ykhvC1OA@kroah.com> (raw)
In-Reply-To: <CAK8P3a19jGTStRnO+em7-7VRwEE-LBL0xY9uqY4+tqx+n04qeQ@mail.gmail.com>
On Thu, Sep 16, 2021 at 08:57:20AM +0200, Arnd Bergmann wrote:
> On Thu, Sep 16, 2021 at 8:40 AM Naresh Kamboju
> <naresh.kamboju@linaro.org> wrote:
> >
> > Following build warnings/ errors noticed while building stable-rc 4.14...5.14
> > branches with gcc-8/9/10/11 for arm architecture with axm55xx_defconfig.
> >
> > # to reproduce this build locally:
> > tuxmake --runtime podman --target-arch arm --toolchain gcc-11
> > --kconfig axm55xx_defconfig
>
> Thank you for the report!
>
> This was introduced in my upstream commit b6e47f3c11c1 ("ARM: 9109/1:
> oabi-compat:
> add epoll_pwait handler") and fixed in the immediately following 249dbe74d3c4
> ("ARM: 9108/1: oabi-compat: rework epoll_wait/epoll_pwait emulation").
>
> Only the first patch got backported to stable-rc, so it's broken
> there. If anyone
> thinks we want to keep the epoll_pwait emulation in stable, I can do a backport,
> but I would just drop that commit from all stable kernels.
Good idea, I'm going to drop it from all stable queues now.
thanks,
greg k-h
prev parent reply other threads:[~2021-09-16 8:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 6:40 ARM: 9109/1: oabi-compat: add epoll_pwait handler Naresh Kamboju
2021-09-16 6:57 ` Arnd Bergmann
2021-09-16 8:41 ` 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=YUMDIUe7ykhvC1OA@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=hch@lst.de \
--cc=naresh.kamboju@linaro.org \
--cc=rmk+kernel@armlinux.org.uk \
--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 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.