On Wed, Apr 27, 2016 at 03:56:56PM +0200, Heiko Stübner wrote:
> Am Mittwoch, 27. April 2016, 14:50:48 schrieb Mark Brown:
> > Any ETA on a fix or should I revert?
> I guess
> [PATCH v4 1/7] regulator: rk808: Add rk808_reg_ops_ranges for LDO3
> from yesterday [0] might be the fix? At least
On Wed, Apr 27, 2016 at 03:56:56PM +0200, Heiko Stübner wrote:
> Am Mittwoch, 27. April 2016, 14:50:48 schrieb Mark Brown:
> > Any ETA on a fix or should I revert?
> I guess
> [PATCH v4 1/7] regulator: rk808: Add rk808_reg_ops_ranges for LDO3
> from yesterday [0] might be the fix? At least
On 27.04.2016 15:50, Mark Brown wrote:
> On Wed, Apr 27, 2016 at 08:35:46AM +0200, Wadim Egorov wrote:
>> On 26.04.2016 21:33, Heiko Stübner wrote:
>>> with this patch applied, 4.6.0-rc5-next-20160426 fails to boot on
>>> rk3288-veyron devices with the bug below. Reverting this one patch
>>>
On 27.04.2016 15:50, Mark Brown wrote:
> On Wed, Apr 27, 2016 at 08:35:46AM +0200, Wadim Egorov wrote:
>> On 26.04.2016 21:33, Heiko Stübner wrote:
>>> with this patch applied, 4.6.0-rc5-next-20160426 fails to boot on
>>> rk3288-veyron devices with the bug below. Reverting this one patch
>>>
Am Mittwoch, 27. April 2016, 14:50:48 schrieb Mark Brown:
> On Wed, Apr 27, 2016 at 08:35:46AM +0200, Wadim Egorov wrote:
> > On 26.04.2016 21:33, Heiko Stübner wrote:
> > > with this patch applied, 4.6.0-rc5-next-20160426 fails to boot on
> > > rk3288-veyron devices with the bug below. Reverting
Am Mittwoch, 27. April 2016, 14:50:48 schrieb Mark Brown:
> On Wed, Apr 27, 2016 at 08:35:46AM +0200, Wadim Egorov wrote:
> > On 26.04.2016 21:33, Heiko Stübner wrote:
> > > with this patch applied, 4.6.0-rc5-next-20160426 fails to boot on
> > > rk3288-veyron devices with the bug below. Reverting
On Wed, Apr 27, 2016 at 08:35:46AM +0200, Wadim Egorov wrote:
> On 26.04.2016 21:33, Heiko Stübner wrote:
> > with this patch applied, 4.6.0-rc5-next-20160426 fails to boot on
> > rk3288-veyron devices with the bug below. Reverting this one patch
> > results in the system booting again:
> This
On Wed, Apr 27, 2016 at 08:35:46AM +0200, Wadim Egorov wrote:
> On 26.04.2016 21:33, Heiko Stübner wrote:
> > with this patch applied, 4.6.0-rc5-next-20160426 fails to boot on
> > rk3288-veyron devices with the bug below. Reverting this one patch
> > results in the system booting again:
> This
On 26.04.2016 21:33, Heiko Stübner wrote:
> Am Montag, 25. April 2016, 18:56:54 schrieb Mark Brown:
>> The patch
>>
>>regulator: rk808: remove linear range definitions with a single range
>>
>> has been applied to the regulator tree at
>>
>>
On 26.04.2016 21:33, Heiko Stübner wrote:
> Am Montag, 25. April 2016, 18:56:54 schrieb Mark Brown:
>> The patch
>>
>>regulator: rk808: remove linear range definitions with a single range
>>
>> has been applied to the regulator tree at
>>
>>
Am Montag, 25. April 2016, 18:56:54 schrieb Mark Brown:
> The patch
>
>regulator: rk808: remove linear range definitions with a single range
>
> has been applied to the regulator tree at
>
>git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
with this patch applied,
Am Montag, 25. April 2016, 18:56:54 schrieb Mark Brown:
> The patch
>
>regulator: rk808: remove linear range definitions with a single range
>
> has been applied to the regulator tree at
>
>git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
with this patch applied,
The patch
regulator: rk808: remove linear range definitions with a single range
has been applied to the regulator tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime
The patch
regulator: rk808: remove linear range definitions with a single range
has been applied to the regulator tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime
14 matches
Mail list logo