From: Philip Li <philip.li@intel.com>
To: Joe Perches <joe@perches.com>
Cc: Dwaipayan Ray <dwaipayanray1@gmail.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Greg KH <gregkh@linuxfoundation.org>,
linux-kernel-mentees@lists.linuxfoundation.org,
linux-kernel <linux-kernel@vger.kernel.org>,
kbuild test robot <lkp@intel.com>
Subject: Re: [Linux-kernel-mentees] Patches from the future - can checkpatch help?
Date: Tue, 2 Feb 2021 22:54:45 +0800 [thread overview]
Message-ID: <20210202145445.GA14043@intel.com> (raw)
In-Reply-To: <d5277573215624098109e888c01f4b10fa917439.camel@perches.com>
On Tue, Feb 02, 2021 at 04:48:04AM -0800, Joe Perches wrote:
> On Mon, 2021-02-01 at 22:41 +0530, Dwaipayan Ray wrote:
> > The idea of a bot seems nice though in general.
> > People do have all the style checking scripts at their disposal, but still
> > we see style issues on the list.
> >
> > Something similar to the kernel test robot, but for style issues seems nice.
> > Is it something the community would like?
>
> (Adding lkp)
>
> Maybe yes, but likely it depends on the particular audience so
> no, not really.
>
> The kbuild test robot used to run checkpatch on patches and there
> there was negative feedback. I don't know if the robot is still
> running checkpatch with some subset of message types.
Hi Joe, we had disabled the checkpatch due to low fruit with very limited
useful reports. Is there any recommendation like which kind of types can
be interested?
Thanks
>
> A thread from 2013:
>
> https://lore.kernel.org/lkml/20130903003958.GA6855@localhost/
>
>
next prev parent reply other threads:[~2021-02-02 15:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 16:34 Patches from the future - can checkpatch help? Dwaipayan Ray
2021-02-01 16:37 ` [Linux-kernel-mentees] " Greg KH
2021-02-01 16:50 ` Lukas Bulwahn
2021-02-01 17:11 ` Dwaipayan Ray
2021-02-02 12:48 ` Joe Perches
2021-02-02 14:54 ` Philip Li [this message]
2021-02-01 17:59 ` Theodore Ts'o
2021-02-01 17:01 ` Dwaipayan Ray
2021-02-02 11:57 ` Greg KH
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=20210202145445.GA14043@intel.com \
--to=philip.li@intel.com \
--cc=dwaipayanray1@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lukas.bulwahn@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