From: Prashant Singh <singhpra@juniper.net>
To: MaeeFilho FL <joaoanandalima@gmail.com>
Cc: Prashant Singh <singhpra@juniper.net>,
Ard Biesheuvel <ardb@kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Jeremy Kerr <jk@ozlabs.org>,
Clark Williams <clrkwllms@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
"Luis Claudio R. Goncalves" <lgoncalv@redhat.com>,
Steve McIntyre <93sam@debian.org>, <linux-efi@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-doc@vger.kernel.org>,
<linux-rt-devel@lists.linux.dev>
Subject: Re: [PATCH v4] efivarfs: add nostatfs mount option to skip QueryVariableInfo()
Date: Mon, 5 Oct 2026 16:35:24 -0700 [thread overview]
Message-ID: <20261005233524.3022-1-singhpra@juniper.net> (raw)
In-Reply-To: <CAFA5sMdHPz-H1EOw3y4RFjHMO9_ZmyV45SwvqF7wh8E4spKujg@mail.gmail.com>
On Sun, Oct 04, 2026 at 11:43:25AM -0300, MaeeFilho FL wrote:
> For the final v5 patch spin, keeping the commit log focused on the
> preemption-disabled context and dropping the verbose raw strace outputs
> as suggested makes the patch documentation extremely tight and industrial
> grade.
Thanks, Joao. Done in v5: the commit log now keeps only the
preemption-disabled rationale and the raw strace dumps are gone.
> No, let's keep it as you suggest.
Done -- kept as-is in v5.
v5 is posted here:
https://lore.kernel.org/all/20261005232250.2620-1-singhpra@juniper.net/
Thanks,
Prashant
prev parent reply other threads:[~2026-10-05 23:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 20:34 Prashant Singh
2026-09-28 20:47 ` sashiko-bot
2026-09-29 6:32 ` Ard Biesheuvel
2026-09-29 7:43 ` Sebastian Andrzej Siewior
2026-09-29 12:22 ` Ard Biesheuvel
2026-09-29 15:14 ` Sebastian Andrzej Siewior
2026-09-30 1:35 ` Prashant Singh
2026-09-30 6:09 ` Ard Biesheuvel
2026-09-30 6:32 ` Sebastian Andrzej Siewior
2026-10-01 1:20 ` Prashant Singh
2026-10-04 7:58 ` Ard Biesheuvel
2026-10-04 14:43 ` MaeeFilho FL
2026-10-05 23:35 ` Prashant Singh [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=20261005233524.3022-1-singhpra@juniper.net \
--to=singhpra@juniper.net \
--cc=93sam@debian.org \
--cc=ardb@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=clrkwllms@kernel.org \
--cc=corbet@lwn.net \
--cc=jk@ozlabs.org \
--cc=joaoanandalima@gmail.com \
--cc=lgoncalv@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=skhan@linuxfoundation.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
all inboxes | Powered by JetHome®