Hi,
* Maciej Purski [180604 14:02]:
> Tony, please apply this patchset and test it on your Beaglebone. It'd be
> great if you could try to find out, which patch causes failure. They should
> be appliable on the current next.
It seems beagle-x15 boots for me except with the last patch in the
Hi,
* Maciej Purski [180604 14:02]:
> Tony, please apply this patchset and test it on your Beaglebone. It'd be
> great if you could try to find out, which patch causes failure. They should
> be appliable on the current next.
It seems beagle-x15 boots for me except with the last patch in the
Hi,
this patchset contains previous two reverted patches. They were split
in order to make it easier to bisect, where the problem lies. It adds
also some simple debugs, which should help us track down the problem.
Tony, please apply this patchset and test it on your Beaglebone. It'd be
great if
Hi,
this patchset contains previous two reverted patches. They were split
in order to make it easier to bisect, where the problem lies. It adds
also some simple debugs, which should help us track down the problem.
Tony, please apply this patchset and test it on your Beaglebone. It'd be
great if
On 30 May 2018 at 20:23, Naresh Kamboju wrote:
> On 30 May 2018 at 20:03, Mark Brown wrote:
>> On Wed, May 30, 2018 at 04:03:15PM +0200, Maciej Purski wrote:
>>
>>> I'm afraid, I have no idea, how to fix it quickly. You can revert it and
>>> in the next version I'll fix the build error and split
On 30 May 2018 at 20:23, Naresh Kamboju wrote:
> On 30 May 2018 at 20:03, Mark Brown wrote:
>> On Wed, May 30, 2018 at 04:03:15PM +0200, Maciej Purski wrote:
>>
>>> I'm afraid, I have no idea, how to fix it quickly. You can revert it and
>>> in the next version I'll fix the build error and split
On 30 May 2018 at 20:03, Mark Brown wrote:
> On Wed, May 30, 2018 at 04:03:15PM +0200, Maciej Purski wrote:
>
>> I'm afraid, I have no idea, how to fix it quickly. You can revert it and
>> in the next version I'll fix the build error and split the last patch even
>> more, so we could perform a
On 30 May 2018 at 20:03, Mark Brown wrote:
> On Wed, May 30, 2018 at 04:03:15PM +0200, Maciej Purski wrote:
>
>> I'm afraid, I have no idea, how to fix it quickly. You can revert it and
>> in the next version I'll fix the build error and split the last patch even
>> more, so we could perform a
* Mark Brown [180530 14:36]:
> On Wed, May 30, 2018 at 04:03:15PM +0200, Maciej Purski wrote:
>
> > I'm afraid, I have no idea, how to fix it quickly. You can revert it and
> > in the next version I'll fix the build error and split the last patch even
> > more, so we could perform a more precise
* Mark Brown [180530 14:36]:
> On Wed, May 30, 2018 at 04:03:15PM +0200, Maciej Purski wrote:
>
> > I'm afraid, I have no idea, how to fix it quickly. You can revert it and
> > in the next version I'll fix the build error and split the last patch even
> > more, so we could perform a more precise
On Wed, May 30, 2018 at 04:03:15PM +0200, Maciej Purski wrote:
> I'm afraid, I have no idea, how to fix it quickly. You can revert it and
> in the next version I'll fix the build error and split the last patch even
> more, so we could perform a more precise bisection. I'd be grateful if you
>
On Wed, May 30, 2018 at 04:03:15PM +0200, Maciej Purski wrote:
> I'm afraid, I have no idea, how to fix it quickly. You can revert it and
> in the next version I'll fix the build error and split the last patch even
> more, so we could perform a more precise bisection. I'd be grateful if you
>
On 05/30/2018 11:13 AM, Mark Brown wrote:
On Tue, May 29, 2018 at 03:15:01PM -0700, Tony Lindgren wrote:
I think I bisected this same issue for the second time now
but for a different merge window. What's up with that?
Last time we just reverted it as Maciej was unable to reproduce your
On 05/30/2018 11:13 AM, Mark Brown wrote:
On Tue, May 29, 2018 at 03:15:01PM -0700, Tony Lindgren wrote:
I think I bisected this same issue for the second time now
but for a different merge window. What's up with that?
Last time we just reverted it as Maciej was unable to reproduce your
On Tue, May 29, 2018 at 03:15:01PM -0700, Tony Lindgren wrote:
> I think I bisected this same issue for the second time now
> but for a different merge window. What's up with that?
Last time we just reverted it as Maciej was unable to reproduce your
problem, he's tried again with some
On Tue, May 29, 2018 at 03:15:01PM -0700, Tony Lindgren wrote:
> I think I bisected this same issue for the second time now
> but for a different merge window. What's up with that?
Last time we just reverted it as Maciej was unable to reproduce your
problem, he's tried again with some
Hi,
Linux next has a regression at least on beaglebone-x15 where
booting Linux hangs shortly after starting init when loading
modules with no output. I bisected it down to commit
456e7cdf3b1a ("regulator: core: Change voltage setting path")
I think I bisected this same issue for the second time
Hi,
Linux next has a regression at least on beaglebone-x15 where
booting Linux hangs shortly after starting init when loading
modules with no output. I bisected it down to commit
456e7cdf3b1a ("regulator: core: Change voltage setting path")
I think I bisected this same issue for the second time
18 matches
Mail list logo
