public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Meyer <thomas@m3y3r.de>
To: David Brown <davidb@codeaurora.org>
Cc: Richard Kuo <rkuo@codeaurora.org>, Arnd Bergmann <arnd@arndb.de>,
	linux-hexagon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Hexagon: Use resource_size function
Date: Thu, 10 Nov 2011 09:39:24 +0100	[thread overview]
Message-ID: <1320914364.20155.10.camel@localhost.localdomain> (raw)
In-Reply-To: <20111109010202.GA16505@huya.qualcomm.com>

Am Dienstag, den 08.11.2011, 17:02 -0800 schrieb David Brown:
> Some minor nits about the formatting of the patch.
> 
> On Tue, Nov 08, 2011 at 07:49:30PM +0100, Thomas Meyer wrote:
> > From: Thomas Meyer <thomas@m3y3r.de>
> 
> Shouldn't need a From: line, since it is the same as the email you
> sent it from.

So do I need a From: line or not?

Documentation/SubmittingPatches says:

        The "from" line must be the very first line in the message body,
        and has the form:
        
                From: Original Author <author@example.com>
        
        The "from" line specifies who will be credited as the author of the
        patch in the permanent changelog.  If the "from" line is missing,
        then the "From:" line from the email header will be used to determine
        the patch author in the changelog.

MUST in the meaning of RFC2119, means it is an absolut requirment. What
should I do?

OTOH some people seems to ignore this, too:

        Do not send more than 15 patches at once to the vger mailing lists!!!

> 
> >  Use resource_size function on resource object
> >  instead of explicit computation.
> 
> The commit text shouldn't be indented.

Will fix that.

> 
> >  The semantic patch that makes this change is available
> >  in scripts/coccinelle/api/resource_size.cocci.
> > 
> >  More information about semantic patching is available at
> >  http://coccinelle.lip6.fr/
> 
> I'm curious if these patches are generated directly by coccinelle,
> since they don't appear to be coming from git.  It'd be nice to have
> diffstats in them (especially when they are larger).

coccinelle doesn't work that way. It's independent from git. I need to
check the manual of spatch.bin if it's possible to produce a diffstat.

> Thanks,
> David
> 




  reply	other threads:[~2011-11-10  8:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-08 18:49 [PATCH] Hexagon: Use resource_size function Thomas Meyer
2011-11-09  1:02 ` David Brown
2011-11-10  8:39   ` Thomas Meyer [this message]
2011-11-10 15:28     ` David Brown
2011-11-09  5:33 ` rkuo

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=1320914364.20155.10.camel@localhost.localdomain \
    --to=thomas@m3y3r.de \
    --cc=arnd@arndb.de \
    --cc=davidb@codeaurora.org \
    --cc=linux-hexagon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rkuo@codeaurora.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