linux-kernel-mentees.lists.linuxfoundation.org archive mirror
 help / color / mirror / Atom feed
From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Dwaipayan Ray <dwaipayanray1@gmail.com>
Cc: linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [Linux-kernel-mentees] [PATCH RFC] checkpatch: fix multistatement macro checks
Date: Wed, 30 Sep 2020 21:37:55 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.21.2009302135580.8279@felia> (raw)
In-Reply-To: <CABJPP5A9hGU=zmQShThBqdj1d4gMWeg2Qza=fgwqk8spQE04Fg@mail.gmail.com>



On Thu, 1 Oct 2020, Dwaipayan Ray wrote:

> On Thu, Oct 1, 2020 at 12:40 AM Lukas Bulwahn <lukas.bulwahn@gmail.com> wrote:
> >
> >
> > Dwaipayan, did you checkpatch.pl your patch before sending it out?
> >
> 
> Oh right! I goofed up! Sorry about that.
> 
> > On Wed, 30 Sep 2020, Dwaipayan Ray wrote:
> >
> > > Checkpatch generates incorrect error message for certain
> > > macros.
> > >
> > > When checkpatch was run on commit 4649079b9de1
> > > "tracing: Make ftrace packed events have align of 1"), it
> >
> > brace ( is missing, checkpatch should warn you.
> >
> 
> Again, I may have been too hasty in sending out the patch :(
>

That is what the linux-kernel-mentees list is for. Send something out 
quickly and have some people with patience check it.

Lukas
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees

      reply	other threads:[~2020-09-30 19:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-29 20:57 [Linux-kernel-mentees] [PATCH RFC] checkpatch: fix multistatement macro checks Dwaipayan Ray
2020-09-30 19:10 ` Lukas Bulwahn
2020-09-30 19:22   ` Dwaipayan Ray
2020-09-30 19:37     ` Lukas Bulwahn [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=alpine.DEB.2.21.2009302135580.8279@felia \
    --to=lukas.bulwahn@gmail.com \
    --cc=dwaipayanray1@gmail.com \
    --cc=linux-kernel-mentees@lists.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).