From: Jonathan Corbet <corbet@lwn.net>
To: Joe Perches <joe@perches.com>,
Dwaipayan Ray <dwaipayanray1@gmail.com>,
mchehab@kernel.org
Cc: linux-kernel-mentees@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v8 0/3] checkpatch: add verbose mode
Date: Mon, 01 Mar 2021 14:57:39 -0700 [thread overview]
Message-ID: <87czwi35bg.fsf@meer.lwn.net> (raw)
In-Reply-To: <70877984ec78d837159dc643e3ae2b05fd91561c.camel@perches.com>
Joe Perches <joe@perches.com> writes:
> On Mon, 2021-03-01 at 14:22 -0700, Jonathan Corbet wrote:
>> Dwaipayan Ray <dwaipayanray1@gmail.com> writes:
>>
>> > Add a new verbose mode to checkpatch. The verbose test
>> > descriptions are read from the new checkpatch documentation
>> > file at `Documentation/dev-tools/checkpatch.rst`, which
>> > is also added by this series.
>>
>> So I can certainly take the doc change, as requested. Remind me,
>> though...should I apply the whole set, or will the checkpatch changes go
>> via another path?
>
> There's no dedicated upstream path for checkpatch.
> So please take the checkpatch changes too.
OK, I have just done that.
Thanks,
jon
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
prev parent reply other threads:[~2021-03-01 21:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 9:38 [PATCH v8 0/3] checkpatch: add verbose mode Dwaipayan Ray
2021-02-26 9:38 ` [PATCH v8 1/3] docs: add documentation for checkpatch Dwaipayan Ray
2021-02-26 9:38 ` [PATCH v8 2/3] checkpatch: add verbose mode Dwaipayan Ray
2021-02-26 9:38 ` [PATCH v8 3/3] MAINTAINERS: clarify responsibility for checkpatch documentation Dwaipayan Ray
2021-03-01 21:22 ` [PATCH v8 0/3] checkpatch: add verbose mode Jonathan Corbet
2021-03-01 21:53 ` Joe Perches
2021-03-01 21:57 ` Jonathan Corbet [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=87czwi35bg.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=dwaipayanray1@gmail.com \
--cc=joe@perches.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@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).