linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: julien.grall@linaro.org (Julien Grall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] arm/arm64: Detect Xen support earlier
Date: Wed, 18 Feb 2015 11:51:25 +0000	[thread overview]
Message-ID: <54E47CBD.7060002@linaro.org> (raw)
In-Reply-To: <1424259059.27775.17.camel@citrix.com>

Hi Ian,

On 18/02/2015 11:30, Ian Campbell wrote:
> On Thu, 2015-02-12 at 06:34 +0000, Julien Grall wrote:
>> Hello,
>>
>> This small patch series move the detection of running on Xen earlier. This is
>> required in order to support earlyprintk via Xen and selecting the preferred
>> console.
>
> Thanks for doing this, having all of the init done in an initcall (even
> a relatively early one) has been a niggle I've wanted address for ages,
> for exactly earlyprintk and preferred console reasons.
>
> I had a very minor comment on #1 but nonetheless both patches:
> Acked-by: Ian Campbell <ian.campbell@citrix.com>

Can I keep you ack on the first one with the __read_mostly dropped?

Regards,

-- 
Julien Grall

  reply	other threads:[~2015-02-18 11:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-12  6:34 [PATCH 0/2] arm/arm64: Detect Xen support earlier Julien Grall
2015-02-12  6:34 ` [PATCH 1/2] arm/xen: Correctly check if the event channel interrupt is present Julien Grall
2015-02-18 11:27   ` Ian Campbell
2015-02-18 11:41     ` Julien Grall
2015-02-18 11:50       ` Julien Grall
2015-02-12  6:34 ` [PATCH 2/2] arm,arm64/xen: move Xen initialization earlier Julien Grall
2015-02-12 11:27 ` [PATCH 0/2] arm/arm64: Detect Xen support earlier Ard Biesheuvel
2015-02-18 11:30 ` Ian Campbell
2015-02-18 11:51   ` Julien Grall [this message]
2015-02-18 12:03     ` Ian Campbell
2015-02-18 12:13       ` Julien Grall
2015-02-18 13:40         ` 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=54E47CBD.7060002@linaro.org \
    --to=julien.grall@linaro.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 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).