From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] arm: update advice on kernel, initramfs and FDT load address.
Date: Wed, 21 Aug 2013 11:21:12 +0100 [thread overview]
Message-ID: <20130821102112.GL17845@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1377080188.31937.53.camel@hastur.hellion.org.uk>
On Wed, Aug 21, 2013 at 11:16:28AM +0100, Ian Campbell wrote:
> On Wed, 2013-08-21 at 11:05 +0100, Russell King - ARM Linux wrote:
> > The only additional thing that needs to be added is a "Kernelversion:"
> > tag to specify which kernel version the patch was generated against.
> > That can go almost anywhere in the message before the actual patch
> > itself.
>
> Cool. Does it understand git tags and stuff? e.g v3.11-rc3 or a sha1?
I'd prefer not full sha1's - the numeric version is normally close enough
to work out where it needs to go should it not apply immediately.
> > Alternatively, if you can remember your web login etc, then you can use
> > the online form, which tries to make it easier (since it generates the
> > formatted email for you - but some people find this method harder.)
>
> I think remembering my web login is probably the biggest barrier for me
> there. In fact remembering the username is probably too much ;-)
Well, I've updated the email address to your current one, so you should
be able to recover the password now.
next prev parent reply other threads:[~2013-08-21 10:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 15:16 [PATCH v2] arm: update advice on kernel, initramfs and FDT load address Ian Campbell
2013-08-08 21:54 ` Will Deacon
2013-08-21 9:59 ` Ian Campbell
2013-08-21 10:05 ` Russell King - ARM Linux
2013-08-21 10:16 ` Ian Campbell
2013-08-21 10:21 ` Russell King - ARM Linux [this message]
2013-08-21 10:31 ` Ian Campbell
2013-08-21 10:43 ` Ian Campbell
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=20130821102112.GL17845@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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 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).