From: Greg KH <gregkh@linuxfoundation.org>
To: Brahmajit Das <listout@listout.xyz>
Cc: stable@kernel.org, linux-kernel-mentees@lists.linux.dev,
skhan@linuxfoundation.org, mpatocka@redhat.com,
stable@vger.kernel.org, patches@lists.linux.dev
Subject: Re: [PATCH 1/1] dm-verity: fix a memory leak if some arguments are specified multiple times
Date: Fri, 6 Jun 2025 08:04:24 +0200 [thread overview]
Message-ID: <2025060654-semisoft-prevent-351a@gregkh> (raw)
In-Reply-To: <65ci7zvx3kr5qfq2ioadzzd4ghrtrtrc3pxefosexxpbup63kb@4jkc6e6usols>
A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Fri, Jun 06, 2025 at 02:00:52AM +0530, Brahmajit Das wrote:
> Greg, Shuah, Mikulas,
> This is my first attempt at backporting an upstream patch (Part of Linux
> kernel Bug Fixing Summer 2025). Please feel free to correct me, I'm open
> to feedback.
> I see I've added two From section, if that requires me to
> resend a v2 of the patch, please let me know.
Yes it does.
But you provide no information as to why this needs to be merged _now_
and not through the normal stable backport process that happens. What
is different here that required you to send it to us?
And you forgot to mention what kernel branch this is for.
There is a stable kernel rules file that explains most of this.
thanks,
greg k-h
next prev parent reply other threads:[~2025-06-06 6:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 20:11 [PATCH 1/1] dm-verity: fix a memory leak if some arguments are specified multiple times Brahmajit Das
2025-06-05 20:30 ` Brahmajit Das
2025-06-06 6:04 ` Greg KH [this message]
2025-06-06 9:07 ` Brahmajit Das
2025-06-06 6:02 ` Greg KH
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=2025060654-semisoft-prevent-351a@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=listout@listout.xyz \
--cc=mpatocka@redhat.com \
--cc=patches@lists.linux.dev \
--cc=skhan@linuxfoundation.org \
--cc=stable@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