On 6/28/2016 2:20 PM, Sebastian Reichel wrote:
> * PGP Signed by an unknown key
>
> Hi,
>
> On Thu, Jun 23, 2016 at 01:43:47PM -0400, Rhyland Klein wrote:
>> On 6/22/2016 10:23 AM, Sebastian Reichel wrote:
>> Is this also going to go into linux-next?
>
>
On 6/28/2016 2:20 PM, Sebastian Reichel wrote:
> * PGP Signed by an unknown key
>
> Hi,
>
> On Thu, Jun 23, 2016 at 01:43:47PM -0400, Rhyland Klein wrote:
>> On 6/22/2016 10:23 AM, Sebastian Reichel wrote:
>> Is this also going to go into linux-next?
>
>
Hi,
On Thu, Jun 23, 2016 at 01:43:47PM -0400, Rhyland Klein wrote:
> On 6/22/2016 10:23 AM, Sebastian Reichel wrote:
> Is this also going to go into linux-next?
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=02184c60eba8491ea574cd17b8ba766c86d468f2
-- Sebastian
Hi,
On Thu, Jun 23, 2016 at 01:43:47PM -0400, Rhyland Klein wrote:
> On 6/22/2016 10:23 AM, Sebastian Reichel wrote:
> Is this also going to go into linux-next?
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=02184c60eba8491ea574cd17b8ba766c86d468f2
-- Sebastian
On 6/22/2016 10:23 AM, Sebastian Reichel wrote:
> * PGP Signed by an unknown key
>
> Hi Rhyland,
>
> On Tue, Jun 21, 2016 at 02:06:55PM -0400, Rhyland Klein wrote:
>> Sebastian, might this be accepted soon? We can't enable the bq27xxx
>> driver for Tegra210 Smaug without running into the crash
On 6/22/2016 10:23 AM, Sebastian Reichel wrote:
> * PGP Signed by an unknown key
>
> Hi Rhyland,
>
> On Tue, Jun 21, 2016 at 02:06:55PM -0400, Rhyland Klein wrote:
>> Sebastian, might this be accepted soon? We can't enable the bq27xxx
>> driver for Tegra210 Smaug without running into the crash
On 6/22/2016 10:23 AM, Sebastian Reichel wrote:
> * PGP Signed by an unknown key
>
> Hi Rhyland,
>
> On Tue, Jun 21, 2016 at 02:06:55PM -0400, Rhyland Klein wrote:
>> Sebastian, might this be accepted soon? We can't enable the bq27xxx
>> driver for Tegra210 Smaug without running into the crash
On 6/22/2016 10:23 AM, Sebastian Reichel wrote:
> * PGP Signed by an unknown key
>
> Hi Rhyland,
>
> On Tue, Jun 21, 2016 at 02:06:55PM -0400, Rhyland Klein wrote:
>> Sebastian, might this be accepted soon? We can't enable the bq27xxx
>> driver for Tegra210 Smaug without running into the crash
Hi Rhyland,
On Tue, Jun 21, 2016 at 02:06:55PM -0400, Rhyland Klein wrote:
> Sebastian, might this be accepted soon? We can't enable the bq27xxx
> driver for Tegra210 Smaug without running into the crash this prevents.
Yes, I have already queued this in my fixes branch some days ago,
but did not
Hi Rhyland,
On Tue, Jun 21, 2016 at 02:06:55PM -0400, Rhyland Klein wrote:
> Sebastian, might this be accepted soon? We can't enable the bq27xxx
> driver for Tegra210 Smaug without running into the crash this prevents.
Yes, I have already queued this in my fixes branch some days ago,
but did not
On 6/9/2016 5:28 PM, Rhyland Klein wrote:
> Change power_supply_read_temp() to use power_supply_get_property()
> so that it will check the use_cnt and ensure it is > 0. The use_cnt
> will be incremented at the end of __power_supply_register, so this
> will block to case where get_property can be
On 6/9/2016 5:28 PM, Rhyland Klein wrote:
> Change power_supply_read_temp() to use power_supply_get_property()
> so that it will check the use_cnt and ensure it is > 0. The use_cnt
> will be incremented at the end of __power_supply_register, so this
> will block to case where get_property can be
On 6/10/2016 5:43 AM, Krzysztof Kozlowski wrote:
> On 06/09/2016 11:28 PM, Rhyland Klein wrote:
>> Change power_supply_read_temp() to use power_supply_get_property()
>> so that it will check the use_cnt and ensure it is > 0. The use_cnt
>> will be incremented at the end of __power_supply_register,
On 6/10/2016 5:43 AM, Krzysztof Kozlowski wrote:
> On 06/09/2016 11:28 PM, Rhyland Klein wrote:
>> Change power_supply_read_temp() to use power_supply_get_property()
>> so that it will check the use_cnt and ensure it is > 0. The use_cnt
>> will be incremented at the end of __power_supply_register,
On 06/09/2016 11:28 PM, Rhyland Klein wrote:
> Change power_supply_read_temp() to use power_supply_get_property()
> so that it will check the use_cnt and ensure it is > 0. The use_cnt
> will be incremented at the end of __power_supply_register, so this
> will block to case where get_property can
On 06/09/2016 11:28 PM, Rhyland Klein wrote:
> Change power_supply_read_temp() to use power_supply_get_property()
> so that it will check the use_cnt and ensure it is > 0. The use_cnt
> will be incremented at the end of __power_supply_register, so this
> will block to case where get_property can
Change power_supply_read_temp() to use power_supply_get_property()
so that it will check the use_cnt and ensure it is > 0. The use_cnt
will be incremented at the end of __power_supply_register, so this
will block to case where get_property can be called before the supply
is fully registered. This
Change power_supply_read_temp() to use power_supply_get_property()
so that it will check the use_cnt and ensure it is > 0. The use_cnt
will be incremented at the end of __power_supply_register, so this
will block to case where get_property can be called before the supply
is fully registered. This
18 matches
Mail list logo