Linus,
here are two i2c driver bugfixes which would be nice to have in 3.17.
Thanks,
Wolfram
The following changes since commit fe82dcec644244676d55a1384c958d5f67979adb:
Linux 3.17-rc7 (2014-09-28 14:29:07 -0700)
are available in the git repository at:
Linus,
here are two i2c driver bugfixes which would be nice to have in 3.17.
Thanks,
Wolfram
The following changes since commit fe82dcec644244676d55a1384c958d5f67979adb:
Linux 3.17-rc7 (2014-09-28 14:29:07 -0700)
are available in the git repository at:
Linus,
this is probably not the kind of pull request you want to see that late
in the cycle. Yet, the ACPI refactorization was problematic again and
caused another two issues which need fixing. My holidays with limited
internet (plus travelling) and the developer's illness didn't help
either :(
Linus,
this is probably not the kind of pull request you want to see that late
in the cycle. Yet, the ACPI refactorization was problematic again and
caused another two issues which need fixing. My holidays with limited
internet (plus travelling) and the developer's illness didn't help
either :(
Linus,
here are I2C driver bugfixes for the 3.17 release. Details can be found
in the commit messages, yet I think this is typical driver stuff. Please
pull.
Thanks,
Wolfram
The following changes since commit 69e273c0b0a3c337a521d083374c918dc52c666f:
Linux 3.17-rc3 (2014-08-31 18:23:04
Linus,
here are I2C driver bugfixes for the 3.17 release. Details can be found
in the commit messages, yet I think this is typical driver stuff. Please
pull.
Thanks,
Wolfram
The following changes since commit 69e273c0b0a3c337a521d083374c918dc52c666f:
Linux 3.17-rc3 (2014-08-31 18:23:04
Linus,
here is the fixup for the 'lowlight' of my last pull request. I2C is not
selected anymore by I2C_ACPI. Instead, the code in question now depends
on I2C=y. Also, Mika has agreed to support me and be the maintainer for
I2C-ACPI related patches. Finally, a new-ID-patch came along last week.
Linus,
here is the fixup for the 'lowlight' of my last pull request. I2C is not
selected anymore by I2C_ACPI. Instead, the code in question now depends
on I2C=y. Also, Mika has agreed to support me and be the maintainer for
I2C-ACPI related patches. Finally, a new-ID-patch came along last week.
On 2014年08月10日 01:34, Linus Torvalds wrote:
> On Sat, Aug 9, 2014 at 6:56 AM, Wolfram Sang wrote:
>>
>> here is the pull request for 3.17 for the I2C subsystem. Highlights:
>
> Lowlight: selecting ACPI support (which used to be the default if ACPI
> was enabled) now forces i2c to be built-in.
>
On 2014年08月10日 01:34, Linus Torvalds wrote:
On Sat, Aug 9, 2014 at 6:56 AM, Wolfram Sang w...@the-dreams.de wrote:
here is the pull request for 3.17 for the I2C subsystem. Highlights:
Lowlight: selecting ACPI support (which used to be the default if ACPI
was enabled) now forces i2c to be
On Sat, Aug 9, 2014 at 6:56 AM, Wolfram Sang wrote:
>
> here is the pull request for 3.17 for the I2C subsystem. Highlights:
Lowlight: selecting ACPI support (which used to be the default if ACPI
was enabled) now forces i2c to be built-in.
I've pulled this, but it's broken. You need to fix it
Linus,
here is the pull request for 3.17 for the I2C subsystem. Highlights:
* class based instantiation finally dropped for most embedded drivers
bringing boot up performance gains
* removed two drivers (one outdated, one a duplicate)
* ACPI has now operation region support (thanks to Lan
Linus,
here is the pull request for 3.17 for the I2C subsystem. Highlights:
* class based instantiation finally dropped for most embedded drivers
bringing boot up performance gains
* removed two drivers (one outdated, one a duplicate)
* ACPI has now operation region support (thanks to Lan
On Sat, Aug 9, 2014 at 6:56 AM, Wolfram Sang w...@the-dreams.de wrote:
here is the pull request for 3.17 for the I2C subsystem. Highlights:
Lowlight: selecting ACPI support (which used to be the default if ACPI
was enabled) now forces i2c to be built-in.
I've pulled this, but it's broken. You
14 matches
Mail list logo
