public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: corentincj@iksaif.net
Cc: linux-acpi@vger.kernel.org, acpi4asus-user@lists.sourceforge.net
Subject: Re: [patch 0/7] New misc/asus-laptop.c driver
Date: Fri, 26 Jan 2007 02:51:04 -0500	[thread overview]
Message-ID: <200701260251.04762.lenb@kernel.org> (raw)
In-Reply-To: <200701251254.34491.corentincj@iksaif.net>

On Thursday 25 January 2007 06:54, Corentin CHARY wrote:
> Hi,
> I've done a lot of work on asus_acpi
Excellent.

A couple of nits on e-mail patch format:

Please fit the comments within 80 lines.
ie. pipe them through fmt -w 68 or something.

The --- in your e-mail should come before the diffstat, not after.

thanks,
-Len

>From Documentation/SubmittingPatches

12) The canonical patch format

The canonical patch subject line is:

    Subject: [PATCH 001/123] subsystem: summary phrase

The canonical patch message body contains the following:

  - A "from" line specifying the patch author.

  - An empty line.

  - The body of the explanation, which will be copied to the
    permanent changelog to describe this patch.

  - The "Signed-off-by:" lines, described above, which will
    also go in the changelog.

  - A marker line containing simply "---".

  - Any additional comments not suitable for the changelog.

...
The "---" marker line serves the essential purpose of marking for patch
handling tools where the changelog message ends.

One good use for the additional comments after the "---" marker is for
a diffstat, to show what files have changed, and the number of inserted
and deleted lines per file.  A diffstat is especially useful on bigger
patches.  Other comments relevant only to the moment or the maintainer,
not suitable for the permanent changelog, should also go here.
Use diffstat options "-p 1 -w 70" so that filenames are listed from the
top of the kernel source tree and don't use too much horizontal space
(easily fit in 80 columns, maybe with some indentation).

  - The actual patch (diff output).
...

  reply	other threads:[~2007-01-26  7:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-25 11:54 [patch 0/7] New misc/asus-laptop.c driver Corentin CHARY
2007-01-26  7:51 ` Len Brown [this message]
2007-01-26 13:04   ` Corentin CHARY
2007-01-30  7:53     ` Len Brown
2007-01-30  8:28       ` Corentin CHARY

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=200701260251.04762.lenb@kernel.org \
    --to=lenb@kernel.org \
    --cc=acpi4asus-user@lists.sourceforge.net \
    --cc=corentincj@iksaif.net \
    --cc=linux-acpi@vger.kernel.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