From: Timur Tabi <timur@freescale.com>
To: Scott Wood <scottwood@freescale.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] drivers/virt: fix dependency on FSL booke hv management driver
Date: Mon, 12 Nov 2012 16:01:50 -0600 [thread overview]
Message-ID: <50A171CE.8080600@freescale.com> (raw)
In-Reply-To: <1352757003-3070-1-git-send-email-scottwood@freescale.com>
Scott Wood wrote:
> If built on non-booke, the build will fail looking for MSR_GS as reported here:
> https://lists.ozlabs.org/pipermail/linuxppc-dev/2012-November/101944.html
>
> Signed-off-by: Scott Wood <scottwood@freescale.com>
> Reported-by: Geert Uytterhoeven <geert@linux-m68k.org>
> Cc: Timur Tabi <timur@freescale.com>
> ---
> Timur, I thought we were going to get rid of that MSR_GS check...
I posted a fix back in May, and I sent Kumar a few reminders over the past
six months. You'll have to ask him why he never applied it.
http://marc.info/?l=linux-kernel&m=133728200626957&w=4
>
> drivers/virt/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/virt/Kconfig b/drivers/virt/Kconfig
> index 2dcdbc9..db5b9e6 100644
> --- a/drivers/virt/Kconfig
> +++ b/drivers/virt/Kconfig
> @@ -14,7 +14,7 @@ if VIRT_DRIVERS
>
> config FSL_HV_MANAGER
> tristate "Freescale hypervisor management driver"
> - depends on FSL_SOC
> + depends on FSL_SOC_BOOKE
> help
> The Freescale hypervisor management driver provides several services
> to drivers and applications related to the Freescale hypervisor:
>
--
Timur Tabi
Linux kernel developer at Freescale
prev parent reply other threads:[~2012-11-12 22:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 21:50 [PATCH] drivers/virt: fix dependency on FSL booke hv management driver Scott Wood
2012-11-12 22:01 ` Timur Tabi [this message]
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=50A171CE.8080600@freescale.com \
--to=timur@freescale.com \
--cc=geert@linux-m68k.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=scottwood@freescale.com \
/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).