From: Joe Perches <joe@perches.com>
To: Aya Mahfouz <mahfouz.saif.elyazal@gmail.com>
Cc: Andy Whitcroft <apw@canonical.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] scripts: checkpatch.pl: add 2 new checks on memset
Date: Sun, 01 Mar 2015 15:45:49 -0800 [thread overview]
Message-ID: <1425253549.31561.9.camel@perches.com> (raw)
In-Reply-To: <20150301233806.GA19189@waves>
On Mon, 2015-03-02 at 01:38 +0200, Aya Mahfouz wrote:
> On Sun, Mar 01, 2015 at 02:13:21PM -0800, Joe Perches wrote:
> > On Sun, 2015-03-01 at 23:43 +0200, Aya Mahfouz wrote:
> > > calls
> > > Reply-To:
> > >
> > > Add 2 new checks on memset calls in the file checkpatch.pl as follows:
> >
> > Hi again Aya
> >
> > The initial 3 lines here aren't necessary.
> >
> > I think it'd be a better subject line with something like
> > "checkpatch: prefer eth_<foo>_addr over memset(,,ETH_ALEN)"
> >
> ok, should I resend it as a fresh patch or send the patch with a new
> subject line and state that it is v4?
Send V4 with new subject and cc Andrew.
> > Please cc Andrew Morton <akpm@linux-foundation.org>
> > And please also don't add Signed-off-by: lines for
> > anyone other than yourself.
> >
> ok, I will cc Andrew. As for your tag, I couldn't take credit
> for the regex that I did not write. Will not do it in the future again
> unless the other side agrees to it.
No worries from me.
"Suggested-by:" or "Portions-by:" or just some text
with "credit to: <name>" for the suggestions, etc
cheers, Joe
prev parent reply other threads:[~2015-03-01 23:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-01 21:43 [PATCH v3] scripts: checkpatch.pl: add 2 new checks on memset Aya Mahfouz
2015-03-01 22:13 ` Joe Perches
2015-03-01 23:38 ` Aya Mahfouz
2015-03-01 23:45 ` 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=1425253549.31561.9.camel@perches.com \
--to=joe@perches.com \
--cc=apw@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mahfouz.saif.elyazal@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