From: Akira Yokosawa <akiyks@gmail.com>
To: weibu@redadmin.org
Cc: Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH -next] docs: submitting-patches: Fix section structure around DCO
Date: Thu, 9 Jul 2026 23:44:43 +0900 [thread overview]
Message-ID: <45664250-b2d1-4dcb-83ca-e76d319c9cdb@gmail.com> (raw)
In-Reply-To: <e942938989f17a884019324412d33031@redadmin.org>
Hi,
On Thu, 09 Jul 2026 19:34:15 +0900, weibu@redadmin.org wrote:
> Maybe it would be better to send this as a follow-up patch after
> the original patch is merged, to avoid unnecessary churn.
What do you mean by "the original patch"?
Confused ...
Thanks, Akira
>
> Thanks,
> Akiyoshi Kurita
[...]
next prev parent reply other threads:[~2026-07-09 14:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 10:44 [PATCH -next] docs: submitting-patches: Fix section structure around DCO Akira Yokosawa
2026-07-08 21:04 ` Randy Dunlap
2026-07-09 10:34 ` weibu
2026-07-09 14:44 ` Akira Yokosawa [this message]
2026-07-09 14:50 ` weibu
2026-07-10 19:46 ` Jonathan Corbet
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=45664250-b2d1-4dcb-83ca-e76d319c9cdb@gmail.com \
--to=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=weibu@redadmin.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