linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ranganath V N <vnranganath.20@gmail.com>
To: rdunlap@infradead.org
Cc: brauner@kernel.org, conor+dt@kernel.org, corbet@lwn.net,
	devicetree@vger.kernel.org, djwong@kernel.org,
	krzk+dt@kernel.org, krzk@kernel.org, kvm@vger.kernel.org,
	laurent.pinchart@ideasonboard.com, linux-doc@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-xfs@vger.kernel.org, pbonzini@redhat.com, robh@kernel.org,
	vnranganath.20@gmail.com
Subject: Re: [PATCH] Documentation: Fix spelling mistakes
Date: Wed,  3 Sep 2025 09:30:43 +0530	[thread overview]
Message-ID: <20250903040043.19398-1-vnranganath.20@gmail.com> (raw)
In-Reply-To: <A33D792E-4773-458B-ACF4-5E66B1FCB5AC@infradead.org>

>On September 2, 2025 12:59:05 PM PDT, Krzysztof Kozlowski <krzk@kernel.org> wrote:
>>On 02/09/2025 21:38, Ranganath V N wrote:
>>> Corrected a few spelling mistakes to improve the readability.
>>> 
>>> Signed-off-by: Ranganath V N <vnranganath.20@gmail.com>
>>> ---
>>>  Documentation/devicetree/bindings/submitting-patches.rst | 2 +-
>>>  Documentation/filesystems/iomap/operations.rst           | 2 +-
>>>  Documentation/virt/kvm/review-checklist.rst              | 2 +-
>>>  3 files changed, 3 insertions(+), 3 deletions(-)
>>> 
>>> diff --git a/Documentation/devicetree/bindings/submitting-patches.rst b/Documentation/devicetree/bindings/submitting-patches.rst
>>> index 46d0b036c97e..191085b0d5e8 100644
>>> --- a/Documentation/devicetree/bindings/submitting-patches.rst
>>> +++ b/Documentation/devicetree/bindings/submitting-patches.rst
>>> @@ -66,7 +66,7 @@ I. For patch submitters
>>>       any DTS patches, regardless whether using existing or new bindings, should
>>>       be placed at the end of patchset to indicate no dependency of drivers on
>>>       the DTS.  DTS will be anyway applied through separate tree or branch, so
>>> -     different order would indicate the serie is non-bisectable.
>>> +     different order would indicate the series is non-bisectable.
>>That's not entirely a spelling mistake
>>https://en.wiktionary.org/wiki/serie#English
>>
>>Best regards,
>>Krzysztof


>Obsolete.  Close enough for me. 

Hi,
Thanks for the response. Do you want me to resend the patch by ignoring this?
particular "serie".

Ranganath

  reply	other threads:[~2025-09-03  4:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-02 19:38 [PATCH] Documentation: Fix spelling mistakes Ranganath V N
2025-09-02 19:47 ` Randy Dunlap
2025-09-02 19:59 ` Krzysztof Kozlowski
2025-09-02 20:05   ` Randy Dunlap
2025-09-03  4:00     ` Ranganath V N [this message]
2025-09-03  4:46       ` Matthew Wilcox
2025-09-03 16:46 ` Rob Herring (Arm)
2025-09-03 21:36 ` 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=20250903040043.19398-1-vnranganath.20@gmail.com \
    --to=vnranganath.20@gmail.com \
    --cc=brauner@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=djwong@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=rdunlap@infradead.org \
    --cc=robh@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;
as well as URLs for NNTP newsgroup(s).