From: arnaud.patard@rtp-net.org (Arnaud Patard (Rtp))
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] orion/kirkwood fixes for v3.6
Date: Wed, 15 Aug 2012 15:10:51 +0200 [thread overview]
Message-ID: <87boicwbac.fsf@lebrac.rtp-net.org> (raw)
In-Reply-To: <201208151237.56639.arnd@arndb.de> (Arnd Bergmann's message of "Wed, 15 Aug 2012 12:37:56 +0000")
Arnd Bergmann <arnd@arndb.de> writes:
Hi,
> On Tuesday 14 August 2012, Jason Cooper wrote:
>> The following changes since commit 0d7614f09c1ebdbaa1599a5aba7593f147bf96ee:
>>
>> Linux 3.6-rc1 (2012-08-02 16:38:10 -0700)
>>
>> are available in the git repository at:
>> git://git.infradead.org/users/jcooper/linux.git fixes-for-v3.6
>>
>
> Pulled, thanks!
>
> As soon as you have a pgp key that is signed by other maintainers,
> I think you should start sending signed tags instead of branches,
> and include a short description for what is in the branch you are
> sending. I've started adding descriptions for every merge I do
> and it's easier for me if I don't have to write it myself.
>
> The first patch in your series (ARM: Orion: Set eth packet size
> csum offload limit) looks like it should apply to older kernels
> as well. In those cases, please add "Cc: stable at vger.kernel.org"
> below the Signed-off-by lines (but not in the email submission)
> so it can get picked up by Greg for the longterm and stable
> releases.
I've not added stable@ in Cc: because it won't apply on most other
kernels. fwiw, I plan to send a backport for 3.2.
Arnaud
next prev parent reply other threads:[~2012-08-15 13:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 23:44 [GIT PULL] orion/kirkwood fixes for v3.6 Jason Cooper
2012-08-15 12:37 ` Arnd Bergmann
2012-08-15 13:10 ` Arnaud Patard (Rtp) [this message]
2012-08-15 13:13 ` Jason Cooper
2012-08-15 13:35 ` Arnd Bergmann
2012-08-15 14:02 ` [GIT PULL V2] " Jason Cooper
2012-08-15 16:19 ` Arnd Bergmann
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=87boicwbac.fsf@lebrac.rtp-net.org \
--to=arnaud.patard@rtp-net.org \
--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.