Hi Wolfram,
On Tue, Feb 17, 2015 at 08:11:58PM +0100, Wolfram Sang wrote:
> Randy,
>
> thanks for the report!
>
> > I suppose someone could make that:
> >
> > depends on I2C_DESIGNWARE_PLATFORM && IOSF_MBI=y && ACPI
> >
> > or even make I2C_DESIGNWARE_BAYTRAIL be a tristate symbol.
>
>
Randy,
thanks for the report!
> I suppose someone could make that:
>
> depends on I2C_DESIGNWARE_PLATFORM && IOSF_MBI=y && ACPI
>
> or even make I2C_DESIGNWARE_BAYTRAIL be a tristate symbol.
I'll wait a day for input from David what he prefers, because I don't
own/know this platform. If
On 02/16/15 21:02, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any material destined for v3.21 to your linux-next
> included trees until after v3.20-rc1 has been released.
>
> Changes since 20150216:
>
on i386, when CONFIG_IOSF_MBI=m and
CONFIG_I2C_DESIGNWARE_BAYTRAIL=y:
On 02/16/15 21:02, Stephen Rothwell wrote:
Hi all,
Please do not add any material destined for v3.21 to your linux-next
included trees until after v3.20-rc1 has been released.
Changes since 20150216:
on i386, when CONFIG_IOSF_MBI=m and
CONFIG_I2C_DESIGNWARE_BAYTRAIL=y:
Randy,
thanks for the report!
I suppose someone could make that:
depends on I2C_DESIGNWARE_PLATFORM IOSF_MBI=y ACPI
or even make I2C_DESIGNWARE_BAYTRAIL be a tristate symbol.
I'll wait a day for input from David what he prefers, because I don't
own/know this platform. If there is
Hi Wolfram,
On Tue, Feb 17, 2015 at 08:11:58PM +0100, Wolfram Sang wrote:
Randy,
thanks for the report!
I suppose someone could make that:
depends on I2C_DESIGNWARE_PLATFORM IOSF_MBI=y ACPI
or even make I2C_DESIGNWARE_BAYTRAIL be a tristate symbol.
I'll wait a day for
6 matches
Mail list logo
