From: Joe Perches <joe@perches.com>
To: Mrinal Pandey <mrinalmni@gmail.com>,
apw@canonical.com, linux-kernel@vger.kernel.org,
lukas.bulwahn@gmail.com, skhan@linuxfoundation.org,
Linux-kernel-mentees@lists.linuxfoundation.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [Linux-kernel-mentees] [PATCH v2] checkpatch: Fix the usage of capture group ( ... )
Date: Thu, 20 Aug 2020 21:25:03 -0700 [thread overview]
Message-ID: <9230a7f0b80b4a984f18c979ca3c703edd7d6f98.camel@perches.com> (raw)
In-Reply-To: <20200820045232.tmun7jlppeeesg4p@mrinalpandey>
On Thu, 2020-08-20 at 10:22 +0530, Mrinal Pandey wrote:
> 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.
https://lore.kernel.org/lkml/20200714032352.f476hanaj2dlmiot@mrinalpandey/
Andrew, can you pick up this patch please.
Thanks
_______________________________________________
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:[~2020-08-21 4:25 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
2020-08-21 4:25 ` Joe Perches [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=9230a7f0b80b4a984f18c979ca3c703edd7d6f98.camel@perches.com \
--to=joe@perches.com \
--cc=Linux-kernel-mentees@lists.linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=mrinalmni@gmail.com \
--cc=skhan@linuxfoundation.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).