From: Maninder Singh <maninder1.s@samsung.com>
To: Joe Perches <joe@perches.com>,
"apw@canonical.com" <apw@canonical.com>,
"dwaipayanray1@gmail.com" <dwaipayanray1@gmail.com>,
"lukas.bulwahn@gmail.com" <lukas.bulwahn@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Vaneet Narang <v.narang@samsung.com>
Subject: RE: [PATCH RESEND v2] scripts/checkpatch.pl: remove _deferred and _deferred_once false warning
Date: Wed, 02 Feb 2022 15:38:16 +0530 [thread overview]
Message-ID: <1167862481.1626207.1643796496590@mail-kr5-2> (raw)
In-Reply-To: <b7f445008e9921f41df36077a7e28562675e8417.camel@perches.com>
[-- Attachment #1: Type: text/plain, Size: 1836 bytes --]
Hi,
> > > > printk_deferred and printk_deferred_once requires LOGLEVEL in argument,
> > > > but checkpatch.pl reports it as warning:
> >
> > > When did that occur? Please reference the specific commit.
> > > When printk_sched (now printk_deferred) was created it did not
> > > allow KERN_<LEVEL>.
> >
> > > see commit 3ccf3e830615 ("printk/sched: Introduce special printk_sched() for those awkward moments")
> >
> > I think with below commit:
> >
> > 98e35f5894cf208084688ec0c7bb7b713efc997f (printk: git rid of [sched_delayed] message for printk_deferred)
> >
> > earlier it was passing hardcoded KERN_WARNING to all printk_deferred messages, but now it switched
> > to normal printk behavior.
> >
> > - if (in_sched)
> > - text_len = scnprintf(text, sizeof(textbuf),
> > - KERN_WARNING "[sched_delayed] ");
> > -
> > - text_len += vscnprintf(text + text_len,
> > - sizeof(textbuf) - text_len, fmt, args);
> > + text_len = vscnprintf(text, sizeof(textbuf), fmt, args);
> >
> >
> > I did not search that earlier, because we were fixing some issue in our local module code with printk_deferred
> > and then checkatch reported the issues, so thought of fixing it, becaue without level
> > pritk_deferred messages was shifted to default loglevel as done by normal printk.
> >
> > So I thought it was designed to pass loglevel from starting stage and checjpatch reports falsely.
> > but seems checkpatch needs to fixed with that commit itself, because earlier it was not required to pass loglevel.
>
> Most of that should be in the commit message.
Yes, Initially I thought it's added in checkpatch by mistake,
I Should have checked history of printk_deferred also.
I will send new version with updated comit message.
Thanks
[-- Attachment #2: rcptInfo.txt --]
[-- Type: application/octet-stream, Size: 1313 bytes --]
=================================================================================================================================
Subject : Re: [PATCH RESEND v2] scripts/checkpatch.pl: remove _deferred and _deferred_once false warning
From : null
Sent Date : 2022-02-02 15:29 GMT+5:30
=================================================================================================================================
Name Type Job Title Dept. Company
=================================================================================================================================
Maninder Singh TO Staff Engineer System S/W Group /SRI-Delhi Samsung Electronics
apw@canonical.com TO
dwaipayanray1@gmail.com TO
lukas.bulwahn@gmail.com TO
linux-kernel@vger.kernel.org CC
Vaneet Narang CC Associate Architect System S/W Group /SRI-Delhi Samsung Electronics
=================================================================================================================================
prev parent reply other threads:[~2022-02-02 10:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220202071414epcas5p1d329ae4f76c281c1f8f7f07bfb36a919@epcas5p1.samsung.com>
2022-02-02 7:14 ` Maninder Singh
2022-02-02 9:16 ` Joe Perches
[not found] ` <CGME20220202071414epcas5p1d329ae4f76c281c1f8f7f07bfb36a919@epcms5p2>
2022-02-02 9:52 ` Maninder Singh
2022-02-02 9:59 ` Joe Perches
[not found] ` <CGME20220202071414epcas5p1d329ae4f76c281c1f8f7f07bfb36a919@epcms5p5>
2022-02-02 10:08 ` Maninder Singh [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=1167862481.1626207.1643796496590@mail-kr5-2 \
--to=maninder1.s@samsung.com \
--cc=apw@canonical.com \
--cc=dwaipayanray1@gmail.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=v.narang@samsung.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®