From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] arm64: don't call early_*map() post paging_init()
Date: Tue, 6 Jan 2015 16:05:12 +0000 [thread overview]
Message-ID: <20150106160511.GD3484@arm.com> (raw)
In-Reply-To: <CAKv+Gu9uWRmLBrnoUNsEcymguiUwgXUc8UVkLO0N21UywuGT=A@mail.gmail.com>
On Tue, Jan 06, 2015 at 03:54:29PM +0000, Ard Biesheuvel wrote:
> On 6 January 2015 at 15:52, Leif Lindholm <leif.lindholm@linaro.org> wrote:
> > On Tue, Jan 06, 2015 at 02:04:50PM +0000, Ard Biesheuvel wrote:
> >> >> Changes since v1:
> >> >> - Rebased to v3.19-rc3
> >> >> - Added 'Fixes:' tags
> >> >> - Reworked 1/2 to restore call to efi_setup_idmap() to the original
> >> >> location in the boot process.
> >> >
> >> > Looks reasonable to me; do they need a CC stable,
> >>
> >> Yes, but with a note that both patches should be taken and the order
> >> is retained, or we break bisect.
> >
> > Where would one add such a note?
> >
>
> I guess the best way would be to not add a 'Cc: stable' tag, but send
> an email to Greg once the patches have been merged by Linus.
I thought Greg didn't take anything until it had hit mainline anyway? I
think it should be fine with just the Cc...
Will
next prev parent reply other threads:[~2015-01-06 16:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 13:41 [PATCH v2 0/2] arm64: don't call early_*map() post paging_init() Leif Lindholm
2015-01-06 13:41 ` [PATCH v2 1/2] arm64: don't make early_*map() calls " Leif Lindholm
2015-01-06 20:35 ` Mark Salter
2015-01-07 10:58 ` Will Deacon
2015-01-07 13:13 ` Ard Biesheuvel
2015-01-07 13:31 ` Leif Lindholm
2015-01-07 19:03 ` Will Deacon
2015-01-06 13:41 ` [PATCH v2 2/2] arm64: call early_ioremap_reset() in paging_init() Leif Lindholm
2015-01-06 13:59 ` [PATCH v2 0/2] arm64: don't call early_*map() post paging_init() Will Deacon
2015-01-06 14:04 ` Ard Biesheuvel
2015-01-06 15:52 ` Leif Lindholm
2015-01-06 15:54 ` Ard Biesheuvel
2015-01-06 16:05 ` Will Deacon [this message]
2015-01-06 16:23 ` Ard Biesheuvel
2015-01-06 19:18 ` Will Deacon
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=20150106160511.GD3484@arm.com \
--to=will.deacon@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 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).