[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <530EB05C.8060803@zytor.com>
Date: Wed, 26 Feb 2014 19:26:20 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: "David E. Box" <david.e.box@...ux.intel.com>, tglx@...utronix.de,
mingo@...hat.com
CC: x86@...nel.org, linux-kernel@...r.kernel.org,
srinivas.pandruvada@...ux.intel.com, jacob.jun.pan@...el.com
Subject: Re: [PATCH V3 2/2] x86: IOSF: Change IOSF_MBI Kconfig to default
y
On 02/26/2014 11:40 AM, David E. Box wrote:
> From: "David E. Box" <david.e.box@...ux.intel.com>
>
> The IOSF Mailbox interface is an access mechanism used by multiple drivers to
> communicate with key configuration registers on new Intel SOC platforms. The
> interface is ubiquitous enough that we need to ensure the availability of the
> driver in non-EXPERT configured x86 kernels.
>
> Signed-off-by: David E. Box <david.e.box@...ux.intel.com>
Hi David,
Could you please update the patch description to explain to people who
may not be familiar why the IOSF driver can't be a module?
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists