linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: rakuram <rakuram.e96@gmail.com>
To: rdunlap@infradead.org
Cc: corbet@lwn.net, linux-doc@vger.kernel.org,
	linux-kernel-mentees@lists.linuxfoundation.org,
	rakuram.e96@gmail.com, skhan@linuxfoundation.org,
	ukleinek@kernel.org
Subject: Re: [PATCH] Documentation/kernel_hacking: Fix minor typo in hacking.rst
Date: Wed, 13 Aug 2025 23:54:33 +0530	[thread overview]
Message-ID: <20250813182434.7189-1-rakuram.e96@gmail.com> (raw)
In-Reply-To: <970be4df-e010-4ba2-b2e9-c2c24b8742ef@infradead.org>

Thanks for the clarification, and I apologise for the oversight in my submission.
Could you please suggest the best way to check whether a similar patch has already been attempted before sending one?

Thanks,
Rakuram

  reply	other threads:[~2025-08-13 18:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-13 17:43 [PATCH] [PATCH] Documentation/kernel_hacking: Fix minor typo in hacking.rst rakuram
2025-08-13 17:48 ` Randy Dunlap
2025-08-13 18:24   ` rakuram [this message]
2025-08-13 19:22     ` Randy Dunlap

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=20250813182434.7189-1-rakuram.e96@gmail.com \
    --to=rakuram.e96@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel-mentees@lists.linuxfoundation.org \
    --cc=rdunlap@infradead.org \
    --cc=skhan@linuxfoundation.org \
    --cc=ukleinek@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).