From: Mrinal Pandey <email@example.com>
To: firstname.lastname@example.org, email@example.com, firstname.lastname@example.org,
Subject: Re: [Linux-kernel-mentees] [PATCH v2] checkpatch: Fix the usage of capture group ( ... )
Date: Thu, 20 Aug 2020 10:22:32 +0530 [thread overview]
Message-ID: <20200820045232.tmun7jlppeeesg4p@mrinalpandey> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 937 bytes --]
On 20/07/30 12:31AM, Joe Perches wrote:
> On Thu, 2020-07-30 at 07:58 +0200, Lukas Bulwahn wrote:
> > Hi Joe,
> > did you see this quick fix to checkpatch.pl? Can you comment on the
> > commit and can we get a quick ack on that fix, please?
> Yes, in a bit.
> > General question on patches for ./scripts/checkpatch.pl:
> > How do they travel to Linus?
> Generally via Andrew Morton.
> > Do you pick those patches and provide them to Andrew Morton?
> > Or do you just ack them and we need to send them to Andrew Morton to get
> > them into mainline?
> Generally, ack and forward.
Did you get the time to check this patch out? This patch is a part of my
mentorship project and your comments on it would help me to make the
best out of this learning process.
Please review it as time permits and let me know if what I propose makes
sense at all.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 201 bytes --]
Linux-kernel-mentees mailing list
next prev parent reply other threads:[~2020-08-20 4:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 3:23 [Linux-kernel-mentees] [PATCH v2] checkpatch: Fix the usage of capture group ( ... ) Mrinal Pandey
2020-07-14 5:47 ` Lukas Bulwahn
2020-07-14 7:37 ` Mrinal Pandey
2020-07-30 5:58 ` Lukas Bulwahn
2020-07-30 7:31 ` Joe Perches
2020-08-20 4:52 ` Mrinal Pandey [this message]
2020-08-21 4:25 ` Joe Perches
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).