From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Sebastian Priebe <sebastian.priebe@konplan.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: AW: BLOCK_LEGACY_AUTOLOAD not default y in Linux 5.15.179+
Date: Fri, 20 Jun 2025 08:53:59 +0200 [thread overview]
Message-ID: <2025062047-matchless-jalapeno-41fc@gregkh> (raw)
In-Reply-To: <ZR0P278MB097420DCEF0AC969D89C37979F7CA@ZR0P278MB0974.CHEP278.PROD.OUTLOOK.COM>
On Fri, Jun 20, 2025 at 06:47:58AM +0000, Sebastian Priebe wrote:
> Hello,
>
> Could somebody please have a look to this request?
It's only been 4 days, please give us a chance to catch up on things.
There hasn't even been a new 5.15.y release since you made this request.
Also, please do not top-post.
thanks,
greg k-h
next prev parent reply other threads:[~2025-06-20 6:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 7:28 BLOCK_LEGACY_AUTOLOAD not default y in Linux 5.15.179+ Sebastian Priebe
2025-06-20 6:47 ` AW: " Sebastian Priebe
2025-06-20 6:53 ` gregkh [this message]
2025-06-20 15:41 ` gregkh
2025-06-23 6:49 ` AW: " Sebastian Priebe
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=2025062047-matchless-jalapeno-41fc@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=sebastian.priebe@konplan.com \
--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