From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux Kernel Tracing <linux-trace-kernel@vger.kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Tomas Glozar <tglozar@redhat.com>,
Crystal Wood <crwood@redhat.com>,
Gopi Krishna Menon <krishnagopi487@gmail.com>
Subject: Re: [PATCH] Documentation/rtla: rename common_xxx.rst files to common_xxx.txt
Date: Sat, 18 Oct 2025 21:30:37 +0700 [thread overview]
Message-ID: <aPOkjdKXDKeIIsCE@archie.me> (raw)
In-Reply-To: <87v7kcz3yl.fsf@trenco.lwn.net>
[-- Attachment #1: Type: text/plain, Size: 470 bytes --]
On Sat, Oct 18, 2025 at 08:20:34AM -0600, Jonathan Corbet wrote:
> Bagas Sanjaya <bagasdotme@gmail.com> writes:
>
> > Shouldn't this more appropriate as a fix for current cycle (6.18)? I see
> > the warnings on Linus's tree, though.
>
> As a general rule, I don't see warning fixes as being important enough
> to send outside of the merge window; the next cycle isn't that far away.
OK, thanks!
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2025-10-18 14:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 9:27 [PATCH] Documentation/rtla: rename common_xxx.rst files to common_xxx.txt Bagas Sanjaya
2025-10-14 3:39 ` Randy Dunlap
2025-10-17 20:27 ` Jonathan Corbet
2025-10-18 5:49 ` Bagas Sanjaya
2025-10-18 14:20 ` Jonathan Corbet
2025-10-18 14:30 ` Bagas Sanjaya [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=aPOkjdKXDKeIIsCE@archie.me \
--to=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=crwood@redhat.com \
--cc=krishnagopi487@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglozar@redhat.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).