From: gregkh <gregkh@linuxfoundation.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Andi Kleen <ak@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
babu.moger@amd.com, Nicolas Pitre <nico@linaro.org>,
Peter Zijlstra <peterz@infradead.org>,
"# 3.4.x" <stable@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Will Deacon <will.deacon@arm.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
stable-commits@vger.kernel.org
Subject: Re: Patch "Kbuild: always define endianess in kconfig.h" has been added to the 4.9-stable tree
Date: Mon, 26 Feb 2018 17:19:10 +0100 [thread overview]
Message-ID: <20180226161910.GB32044@kroah.com> (raw)
In-Reply-To: <CAK8P3a1b+vjTn2+Rmh2WNu4aW9TSrKPJyhysJG-RmfAit6GJ8w@mail.gmail.com>
On Mon, Feb 26, 2018 at 05:14:04PM +0100, Arnd Bergmann wrote:
> On Mon, Feb 26, 2018 at 5:09 PM, <gregkh@linuxfoundation.org> wrote:
>
> > All of the above are caused by include/asm-generic/qrwlock_types.h
> > failing to include asm/byteorder.h after commit e0d02285f16e
> > ("locking/qrwlock: Use 'struct qrwlock' instead of 'struct __qrwlock'")
> > in linux-4.15.
> >
> > Similar bugs may or may not exist in older kernels as well, but there is
> > no easy way to test those with link-time optimizations, and kernels
> > before 4.14 are harder to fix because they don't have Babu's patch
> > series
>
> As I wrote in the changelog, it's probably not a good idea to have this
> backported to 4.9 or earlier, please drop it.
Oops, missed that, now dropped, thanks.
greg k-h
prev parent reply other threads:[~2018-02-26 16:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 16:09 Patch "Kbuild: always define endianess in kconfig.h" has been added to the 4.9-stable tree gregkh
2018-02-26 16:14 ` Arnd Bergmann
2018-02-26 16:19 ` gregkh [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=20180226161910.GB32044@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=babu.moger@amd.com \
--cc=nico@linaro.org \
--cc=peterz@infradead.org \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=will.deacon@arm.com \
--cc=yamada.masahiro@socionext.com \
/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