linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: grant.likely@secretlab.ca (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3 1/5] ARM: kirkwood: Basic support for DNS-320 and DNS-325
Date: Fri, 06 Apr 2012 16:43:13 -0700	[thread overview]
Message-ID: <20120406234313.A040E3E127F@localhost> (raw)
In-Reply-To: <201203280820.00139.arnd@arndb.de>

On Wed, 28 Mar 2012 08:19:59 +0000, Arnd Bergmann <arnd@arndb.de> wrote:
> On Tuesday 27 March 2012, Jamie Lentin wrote:
> > Add support for the DNS-320 and DNS-325. Describe as much as currently possible
> > in the devicetree files, create a board-dnskw.c for everything else.
> > 
> > Use IEEE-compliant "okay", rather than "ok"
> > 
> > Acked-by: Arnd Bergmann <arnd@arndb.de>
> > Acked-by: Jason Cooper <jason@lakedaemon.net>
> > Signed-off-by: Jamie Lentin <jm@lentin.co.uk>
> > ---
> 
> One small note about changeset comments: The part about differences from the previous
> version of the same patch normally goes below the '---' line, in front of the diffstat,
> to prevent it from going into the git changelog. Otherwise people will have no idea
> what it's about.

Counter point on that.  I ask submitters to put the changelog before
the --- because I want it in the commit text.  It is actually helpful
when trying to determine exactly which iteration of a patch series got
committed.

But, different maintainers have different policies so there really
isn't much submitters can do here except ask the maintainer they are
submitting to which approach they prefer.

g.

-- 
Grant Likely, B.Sc, P.Eng.
Secret Lab Technologies,Ltd.

  reply	other threads:[~2012-04-06 23:43 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-27 21:54 [PATCH V3 0/5] Add support for DNS-320 and DNS-325 using devicetree Jamie Lentin
2012-03-27 21:54 ` [PATCH V3 1/5] ARM: kirkwood: Basic support for DNS-320 and DNS-325 Jamie Lentin
2012-03-28  8:19   ` Arnd Bergmann
2012-04-06 23:43     ` Grant Likely [this message]
2012-04-09 14:09       ` Arnd Bergmann
2012-04-09 14:20         ` Jamie Lentin
2012-04-09 15:01           ` Arnd Bergmann
2012-03-31  1:30   ` Jason Cooper
2012-04-06 23:49   ` Grant Likely
2012-04-09 13:20     ` Jamie Lentin
2012-04-09 14:14       ` Arnd Bergmann
2012-04-11  0:43       ` Jason Cooper
2012-04-11 13:32         ` Jamie Lentin
2012-04-11 14:11           ` Jason Cooper
2012-04-11 15:08             ` Arnd Bergmann
2012-04-09 21:27     ` Russell King - ARM Linux
2012-04-11  0:35     ` Jason Cooper
2012-03-27 21:54 ` [PATCH V3 2/5] mtd: Add orion_nand devicetree bindings Jamie Lentin
2012-03-28 23:04   ` Grant Likely
2012-03-27 21:54 ` [PATCH V3 3/5] ARM: kirkwood: Allow nand to be configured via. devicetree Jamie Lentin
2012-03-27 21:54 ` [PATCH V3 4/5] ARM: kirkwood: Define DNS-320/DNS-325 NAND in fdt Jamie Lentin
2012-03-27 21:54 ` [PATCH V3 5/5] mtd: Move fdt partition documentation to a seperate file Jamie Lentin
2012-03-28  8:17   ` Arnd Bergmann
2012-03-28 23:08     ` Grant Likely
2012-03-28 14:41   ` Jason Cooper

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=20120406234313.A040E3E127F@localhost \
    --to=grant.likely@secretlab.ca \
    --cc=linux-arm-kernel@lists.infradead.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).