All of lore.kernel.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: CSR: minor fixes for 3.9-rc1
Date: Mon, 11 Mar 2013 21:13:24 +0000	[thread overview]
Message-ID: <201303112113.24583.arnd@arndb.de> (raw)
In-Reply-To: <CAGsJ_4zyW+jVwDZDTb3TwY9TL+pmub4KGP6K0pgwToa-M2kXxQ@mail.gmail.com>

On Wednesday 06 March 2013, Barry Song wrote:
> Hi Olof, Arnd,
> 
> The following changes since commit 6dbe51c251a327e012439c4772097a13df43c5b8:
> 
>   Linux 3.9-rc1 (2013-03-03 15:11:05 -0800)
> 
> are available in the git repository at:
>   git://gitorious.org/sirfprima2-kernel/sirfprima2-kernel.git sirf/fixes
> 
> Barry Song (1):
>       ARM: prima2: fix a checkpatch issue
> 
> Syam Sidhardhan (1):
>       ARM: prima2: Replace include linux/module.h with linux/export.h
> 
>  arch/arm/mach-prima2/common.c |    4 ++--
>  arch/arm/mach-prima2/pm.c     |    2 +-
>  2 files changed, 3 insertions(+), 3 deletions(-)

Hi Barry,

Sorry for taking a little longer to look at these patches. I decided
not to apply them because they are only cosmetic changes and can wait
for 3.10.

There are a few things that I'd like you to improve in the future:

* Do not include "Change-Id:" tags in the changelog, those are meaningless
  to the upstream kernel.

* Use a signed tag for pull requests, rather than a branch, and try to
  get your gpg key signed by other maintainers when you meet them at
  a conference.

* In the tag description, give an overview of the patches you are
  asking to be pulled. Most people get it right these days, so there
  are lots of examples for you to look at.

	Arnd

  reply	other threads:[~2013-03-11 21:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-06 15:01 [GIT PULL] ARM: CSR: minor fixes for 3.9-rc1 Barry Song
2013-03-11 21:13 ` Arnd Bergmann [this message]
2013-03-12  1:51   ` Barry Song

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=201303112113.24583.arnd@arndb.de \
    --to=arnd@arndb.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.