From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Jonathan Austin <jonathan.austin@arm.com>
Cc: "André Hentschel" <nerv@dawncrow.de>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"Will Deacon" <Will.Deacon@arm.com>
Subject: Re: [PATCH v5] arm: Preserve the user r/w register TPIDRURW on context switch and fork
Date: Fri, 7 Jun 2013 21:28:18 +0100 [thread overview]
Message-ID: <20130607202818.GB18614@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <51B22F01.3030905@arm.com>
On Fri, Jun 07, 2013 at 08:05:37PM +0100, Jonathan Austin wrote:
> If you're using git-format-patch and git-send-email then the main point
> to note is the need to add the KernelVersion: tag described in that
> documentation and also that Russell doesn't want '[Patch]' tags in
> subject lines.
The main thing is the kernelversion: tag, which can appear anywhere before
the patch diff itself. [PATCH] stuff in the subject line is ignored and
removed.
> There's a form for creating yourself an account on the patch system at
> http://www.arm.linux.org.uk/developer/patches/add.php - I'm not actually
> sure that an account is necessary to submit via email - but I *do* have
> one and I've only ever used email so I suspect it might be!
Yes, the system automatically creates an "account" on the initial email -
it's not really an "account" from the email side, but just a name/email
association with the patch itself, which can then be "converted" to an
"account" for the website by the addition of a password.
next prev parent reply other threads:[~2013-06-07 20:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 21:04 [PATCH v5] arm: Preserve the user r/w register TPIDRURW on context switch and fork André Hentschel
2013-05-22 21:04 ` André Hentschel
2013-06-07 19:05 ` Jonathan Austin
2013-06-07 20:28 ` Russell King - ARM Linux [this message]
2013-06-17 8:26 ` Russell King - ARM Linux
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=20130607202818.GB18614@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=Will.Deacon@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonathan.austin@arm.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nerv@dawncrow.de \
/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).