The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Petr Mladek <pmladek@suse.com>
To: Naveen Kumar Chaudhary <naveen.osdev@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] printk: fix typos in comments
Date: Tue, 2 Jun 2026 15:38:55 +0200	[thread overview]
Message-ID: <ah7c782j4fP77PTW@pathway> (raw)
In-Reply-To: <pakfewagyzb7da3yuxnaxdaoma5w4j2c7i3xebmcld3xy4mqs5@zxsx2idpxrdq>

On Mon 2026-06-01 09:26:26, Naveen Kumar Chaudhary wrote:
> Fix spelling/grammatical errors in printk.c and nbcon.c:
> - "precation" -> "precautionary"
> - "othrewise" -> "otherwise"
> - "An usable" -> "A usable"
> - "made a progress" -> "made progress"
> - "preemtible" -> "preemptible"
> - "mechasism" -> "mechanism"
> - "ownerhip" -> "ownership"
> 
> Signed-off-by: Naveen Kumar Chaudhary <naveen.osdev@gmail.com>

JFYI, the patch has been committed into printk/linux.git,
branch for-7.2.

Best Regards,
Petr

      reply	other threads:[~2026-06-02 13:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-01  3:56 [PATCH] printk: fix typos in comments Naveen Kumar Chaudhary
2026-06-02 13:38 ` Petr Mladek [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=ah7c782j4fP77PTW@pathway \
    --to=pmladek@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=naveen.osdev@gmail.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