[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200824173502.GA1161855@kroah.com>
Date: Mon, 24 Aug 2020 19:35:02 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Michael Kelley <mikelley@...rosoft.com>
Cc: will@...nel.org, ardb@...nel.org, arnd@...db.de,
catalin.marinas@....com, mark.rutland@....com, maz@...nel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-hyperv@...r.kernel.org, linux-efi@...r.kernel.org,
linux-arch@...r.kernel.org, wei.liu@...nel.org,
vkuznets@...hat.com, kys@...rosoft.com, sunilmut@...rosoft.com,
boqun.feng@...il.com
Subject: Re: [PATCH v7 09/10] arm64: efi: Export screen_info
On Mon, Aug 24, 2020 at 09:46:22AM -0700, Michael Kelley wrote:
> The Hyper-V frame buffer driver may be built as a module, and
> it needs access to screen_info. So export screen_info.
>
> Signed-off-by: Michael Kelley <mikelley@...rosoft.com>
> ---
> arch/arm64/kernel/efi.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm64/kernel/efi.c b/arch/arm64/kernel/efi.c
> index d0cf596..8ff557a 100644
> --- a/arch/arm64/kernel/efi.c
> +++ b/arch/arm64/kernel/efi.c
> @@ -55,6 +55,7 @@ static __init pteval_t create_mapping_protection(efi_memory_desc_t *md)
>
> /* we will fill this structure from the stub, so don't put it in .bss */
> struct screen_info screen_info __section(.data);
> +EXPORT_SYMBOL(screen_info);
EXPORT_SYMBOL_GPL()?
I have to ask :)
thanks,
greg k-h
Powered by blists - more mailing lists