From: Jonathan Corbet <corbet@lwn.net>
To: Ivan Orlov <ivan.orlov0322@gmail.com>,
Amit Vadhavana <av2082000@gmail.com>,
linux-doc@vger.kernel.org, ricardo@marliere.net
Cc: linux-kernel-mentees@lists.linux.dev, skhan@linuxfoundation.org,
amelie.delaunay@foss.st.com, mcoquelin.stm32@gmail.com,
alexandre.torgue@foss.st.com, catalin.marinas@arm.com,
will@kernel.org, mpe@ellerman.id.au, npiggin@gmail.com,
christophe.leroy@csgroup.eu, naveen@kernel.org,
paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, dave.hansen@linux.intel.com, x86@kernel.org,
hpa@zytor.com, bhelgaas@google.com, conor.dooley@microchip.com,
costa.shul@redhat.com, dmaengine@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org, workflows@vger.kernel.org
Subject: Re: [PATCH] Documentation: Fix spelling mistakes
Date: Sun, 11 Aug 2024 14:11:59 -0600 [thread overview]
Message-ID: <87h6bqbz00.fsf@trenco.lwn.net> (raw)
In-Reply-To: <13beb34b-3ff7-4b88-876f-0a7f65254970@gmail.com>
Ivan Orlov <ivan.orlov0322@gmail.com> writes:
> On 8/10/24 19:32, Amit Vadhavana wrote:
>> Corrected spelling mistakes in the documentation to improve readability.
>>
>
> Hi Amit,
>
> Since this patch contains changes for multiple files from different
> subsystems, it should be divided into file-specific changes (so you have
> one patch per updated file).
Often that is the best thing to do but, honestly, in this case I think I
should just take the set through the docs tree. I don't see much point
in making things harder.
Thanks,
jon
next prev parent reply other threads:[~2024-08-11 20:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-10 18:32 Amit Vadhavana
2024-08-10 20:22 ` Ivan Orlov
2024-08-11 20:11 ` Jonathan Corbet [this message]
2024-08-16 22:21 ` 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=87h6bqbz00.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=alexandre.torgue@foss.st.com \
--cc=amelie.delaunay@foss.st.com \
--cc=aou@eecs.berkeley.edu \
--cc=av2082000@gmail.com \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=conor.dooley@microchip.com \
--cc=costa.shul@redhat.com \
--cc=dave.hansen@linux.intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=hpa@zytor.com \
--cc=ivan.orlov0322@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=naveen@kernel.org \
--cc=npiggin@gmail.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=ricardo@marliere.net \
--cc=skhan@linuxfoundation.org \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
--cc=workflows@vger.kernel.org \
--cc=x86@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