public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Steve Sakoman <sakoman@gmail.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: ARM: OMAP: Overo: use new gpmc nand infrastructure
Date: Wed, 07 Apr 2010 13:33:53 -0700	[thread overview]
Message-ID: <87k4sjatou.fsf@deeprootsystems.com> (raw)
In-Reply-To: <u2t5e088bd91004071208o10ac1cf3seecb89b4e29c9ac4@mail.gmail.com> (Steve Sakoman's message of "Wed\, 7 Apr 2010 12\:08\:17 -0700")

Steve Sakoman <sakoman@gmail.com> writes:

> On Wed, Apr 7, 2010 at 10:41 AM, Kevin Hilman
> <khilman@deeprootsystems.com> wrote:
>> Steve Sakoman <steve@sakoman.com> writes:
>>
>>> From: Steve Sakoman <steve@sakoman.com>
>>>
>>> Signed-off-by: Steve Sakoman <steve@sakoman.com>
>>
>> -ENOCHANGELOG
>>
>> Please add descriptive changelog.  Otherwise, looks like a good
>> cleanup.
>
> I assume you looking for something like:
>
> Restores nand functionality after changes in commit
> 2f70a1e93657bea0baa7d449aa49e44a08582dc8

Personally, I'd rather see a text summary of the commit (plus commit
ID) so I don't have to follow a commit ID unless I really want the
details.  Something like:

"A new GPMC NAND infrastructure was added by commit foo.  This patch
updates Overo NAND functionally to work with those changes."

or similar.  Since the changelogs become permanent git history, it's
important that they be descriptive and useful long after the initial
commits are done and we've all forgotten about the details.

> If so I'll add it after waiting a bit for any other comments.  I
> assume you are also OK with the similar patch for Beagleboard?

Yes, with a good changelog.  ;)


-- Kevin (changelog cop) Hilman

      reply	other threads:[~2010-04-07 20:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-07 17:35 ARM: OMAP: Overo: use new gpmc nand infrastructure Steve Sakoman
2010-04-07 17:41 ` Kevin Hilman
2010-04-07 19:08   ` Steve Sakoman
2010-04-07 20:33     ` Kevin Hilman [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=87k4sjatou.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=sakoman@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