From: Hugh Dickins <hughd@google.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Nathan Chancellor <nathan@kernel.org>,
Sasha Levin <sashal@kernel.org>, Hugh Dickins <hughd@google.com>,
llvm@lists.linux.dev, stable@vger.kernel.org
Subject: Re: [PATCH 5.4 and earlier only] mm: Fix '.data.once' orphan section warning
Date: Sat, 3 Dec 2022 09:41:34 -0800 (PST) [thread overview]
Message-ID: <5f9317c7-e899-a6b2-dd23-664a1b6d629@google.com> (raw)
In-Reply-To: <Y4tQYgjDgodwR2pP@kroah.com>
On Sat, 3 Dec 2022, Greg Kroah-Hartman wrote:
> On Mon, Nov 28, 2022 at 03:53:46PM -0700, Nathan Chancellor wrote:
> >
> > As far as I can tell, this should be applied to 5.4 and earlier. It
> > should apply cleanly but let me know if not.
>
> Queued up everywhere, thanks.
Thanks for queueing them up, Greg, but please read through the thread:
I have doubts on the 4.14 and 4.9 ones, which would want a different patch
if we're going to make any change; but thought we could just leave those
trees without the patch, and Nathan agreed.
Thanks,
Hugh
next prev parent reply other threads:[~2022-12-03 17:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 22:53 [PATCH 5.4 and earlier only] mm: Fix '.data.once' orphan section warning Nathan Chancellor
2022-11-30 6:28 ` Hugh Dickins
2022-11-30 16:20 ` Nathan Chancellor
2022-12-03 13:34 ` Greg Kroah-Hartman
2022-12-03 17:41 ` Hugh Dickins [this message]
2022-12-04 15:38 ` Greg Kroah-Hartman
2022-12-04 15:55 ` Hugh Dickins
2022-12-03 13:54 ` Patch "mm: Fix '.data.once' orphan section warning" has been added to the 4.9-stable tree gregkh
2022-12-03 13:54 ` Patch "mm: Fix '.data.once' orphan section warning" has been added to the 4.14-stable tree gregkh
2022-12-03 13:55 ` Patch "mm: Fix '.data.once' orphan section warning" has been added to the 4.19-stable tree gregkh
2022-12-03 13:55 ` Patch "mm: Fix '.data.once' orphan section warning" has been added to the 5.4-stable tree gregkh
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=5f9317c7-e899-a6b2-dd23-664a1b6d629@google.com \
--to=hughd@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--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