From: Greg KH <gregkh@linuxfoundation.org>
To: Minu Jin <s9430939@naver.com>
Cc: arnd@arndb.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] char: mem: fix typo and use pr_err() for logging
Date: Fri, 16 Jan 2026 16:28:52 +0100 [thread overview]
Message-ID: <2026011646-disengage-enticing-4f86@gregkh> (raw)
In-Reply-To: <20260102062759.3749606-1-s9430939@naver.com>
On Fri, Jan 02, 2026 at 03:27:59PM +0900, Minu Jin wrote:
> Fix a typo in the comment of read_mem(): funcion -> function
>
> Replace a raw printk() call in chr_dev_init() with pr_err().
> The original call lacked a log level, which is discouraged.
>
> Using pr_err() ensures the error is properly categorized and
> follows modern logging practices.
This is two different things, it should be 2 different patches (yes, I'm
being pedantic, sorry, that's because:)
> if (register_chrdev(MEM_MAJOR, "mem", &memory_fops))
> - printk("unable to get major %d for memory devs\n", MEM_MAJOR);
> + pr_err("unable to get major %d for memory devs\n", MEM_MAJOR);
This change doesn't really do anything different, so it's not needed.
Let's leave it alone as it's been this way for decades.
thanks,
greg k-h
prev parent reply other threads:[~2026-01-16 15:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-02 6:27 Minu Jin
2026-01-16 15:28 ` Greg KH [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=2026011646-disengage-enticing-4f86@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=s9430939@naver.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
all inboxes | Powered by JetHome®