From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] arm/smp: Absorb boot_secondary()
Date: Fri, 22 Aug 2014 14:33:16 +0100 [thread overview]
Message-ID: <20140822133315.GC20583@arm.com> (raw)
In-Reply-To: <CAMuHMdVp3xeJ2nDYJ00tLc7HuZ5v+jC-T8omWV5+G_3C8XoyoA@mail.gmail.com>
On Wed, Aug 20, 2014 at 08:55:33PM +0100, Geert Uytterhoeven wrote:
> Has anyone already written a "git-send-email"-compatible script to
> submit patches there?
You can send patches as usual to patches at arm.linux.org.uk, just add
KernelVersion: v3.?? after the --- line in your patch (maybe this could
be automate as well but I didn't bother).
For series, because the arrival order is not guaranteed, I use the git
alias below to trick it into sleeping 60s between patches:
ksend-rmk-patch = !git send-email --annotate --no-thread --suppress-cc=all --to-cmd='sleep 60 && echo patches at arm.linux.org.uk "#"'
For stgit, I have a dedicated template:
From: %(sender)s
To: patches at arm.linux.org.uk
Subject: %(prefix)s%(shortdescr)s
%(longdescr)s
PATCH FOLLOWS
KernelVersion:%(version)s
%(diff)s
And there is always git pull request that Russell is happy with.
--
Catalin
WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
Russell King <linux@arm.linux.org.uk>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] arm/smp: Absorb boot_secondary()
Date: Fri, 22 Aug 2014 14:33:16 +0100 [thread overview]
Message-ID: <20140822133315.GC20583@arm.com> (raw)
In-Reply-To: <CAMuHMdVp3xeJ2nDYJ00tLc7HuZ5v+jC-T8omWV5+G_3C8XoyoA@mail.gmail.com>
On Wed, Aug 20, 2014 at 08:55:33PM +0100, Geert Uytterhoeven wrote:
> Has anyone already written a "git-send-email"-compatible script to
> submit patches there?
You can send patches as usual to patches@arm.linux.org.uk, just add
KernelVersion: v3.?? after the --- line in your patch (maybe this could
be automate as well but I didn't bother).
For series, because the arrival order is not guaranteed, I use the git
alias below to trick it into sleeping 60s between patches:
ksend-rmk-patch = !git send-email --annotate --no-thread --suppress-cc=all --to-cmd='sleep 60 && echo patches@arm.linux.org.uk "#"'
For stgit, I have a dedicated template:
From: %(sender)s
To: patches@arm.linux.org.uk
Subject: %(prefix)s%(shortdescr)s
%(longdescr)s
PATCH FOLLOWS
KernelVersion:%(version)s
%(diff)s
And there is always git pull request that Russell is happy with.
--
Catalin
next prev parent reply other threads:[~2014-08-22 13:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 15:01 [PATCH v3] arm/smp: Absorb boot_secondary() Geert Uytterhoeven
2014-07-09 15:01 ` Geert Uytterhoeven
2014-08-20 15:51 ` Geert Uytterhoeven
2014-08-20 15:51 ` Geert Uytterhoeven
2014-08-20 19:30 ` Arnd Bergmann
2014-08-20 19:30 ` Arnd Bergmann
2014-08-20 19:55 ` Geert Uytterhoeven
2014-08-20 19:55 ` Geert Uytterhoeven
2014-08-22 13:33 ` Catalin Marinas [this message]
2014-08-22 13:33 ` Catalin Marinas
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=20140822133315.GC20583@arm.com \
--to=catalin.marinas@arm.com \
--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.