From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Tom Saeger <tom.saeger@oracle.com>
Cc: stable@vger.kernel.org, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.15 v2 0/5] Fix Build ID on arm64 if CONFIG_MODVERSIONS=y
Date: Wed, 22 Feb 2023 07:01:20 +0100 [thread overview]
Message-ID: <Y/WvsGwUfsenunAw@kroah.com> (raw)
In-Reply-To: <20230221230225.cll4lfsxhv2s4sms@oracle.com>
On Tue, Feb 21, 2023 at 05:02:25PM -0600, Tom Saeger wrote:
> On Fri, Feb 10, 2023 at 01:18:39PM -0700, Tom Saeger wrote:
>
> I double-checked submission procedures and I believe everything is correct,
> is there anything I still need to do?
Not top-post and have patience? :)
They are in my queue, I wanted to wait until we had a "quieter" release
to put them in to make it easier to handle when this problamatic series
is let loose on all of the builders.
thanks,
greg k-h
next prev parent reply other threads:[~2023-02-22 6:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 20:18 [PATCH 5.15 v2 0/5] Fix Build ID on arm64 if CONFIG_MODVERSIONS=y Tom Saeger
2023-02-10 20:18 ` [PATCH 5.15 v2 1/5] arch: fix broken BuildID for arm64 and riscv Tom Saeger
2023-02-23 9:51 ` Greg Kroah-Hartman
2023-02-23 17:53 ` Tom Saeger
2023-02-24 2:47 ` Tom Saeger
2023-02-28 8:58 ` Greg Kroah-Hartman
2023-02-10 20:18 ` [PATCH 5.15 v2 2/5] powerpc/vmlinux.lds: Define RUNTIME_DISCARD_EXIT Tom Saeger
2023-02-10 20:18 ` [PATCH 5.15 v2 3/5] powerpc/vmlinux.lds: Don't discard .rela* for relocatable builds Tom Saeger
2023-02-10 20:18 ` [PATCH 5.15 v2 4/5] s390: define RUNTIME_DISCARD_EXIT to fix link error with GNU ld < 2.36 Tom Saeger
2023-02-10 20:18 ` [PATCH 5.15 v2 5/5] sh: define RUNTIME_DISCARD_EXIT Tom Saeger
2023-02-21 23:02 ` [PATCH 5.15 v2 0/5] Fix Build ID on arm64 if CONFIG_MODVERSIONS=y Tom Saeger
2023-02-22 6:01 ` Greg Kroah-Hartman [this message]
2023-02-22 18:02 ` Tom Saeger
2023-02-23 9:55 ` Greg Kroah-Hartman
2023-02-23 18:04 ` Tom Saeger
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=Y/WvsGwUfsenunAw@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tom.saeger@oracle.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;
as well as URLs for NNTP newsgroup(s).