On Fri, Sep 15, 2017 at 12:29 PM, Andy Lutomirski wrote:
>
>
>> On Sep 15, 2017, at 11:47 AM, Linus Torvalds
>> wrote:
>>
>>> On Fri, Sep 15, 2017 at 3:22 AM, Pavel Machek wrote:
>>>
>>> Let me pull latest...
>>>
>>> 711aab1dbb324d321e3d84368a435a78908c7bce
>>>
>>> (Strange. Not authored by Lin
> On Sep 15, 2017, at 11:47 AM, Linus Torvalds
> wrote:
>
>> On Fri, Sep 15, 2017 at 3:22 AM, Pavel Machek wrote:
>>
>> Let me pull latest...
>>
>> 711aab1dbb324d321e3d84368a435a78908c7bce
>>
>> (Strange. Not authored by Linus and old?)
>
> That's the author date, the committer date is ne
On Fri, Sep 15, 2017 at 3:22 AM, Pavel Machek wrote:
>
> Let me pull latest...
>
> 711aab1dbb324d321e3d84368a435a78908c7bce
>
> (Strange. Not authored by Linus and old?)
That's the author date, the committer date is new. Top of tree right
now just happens to be a patch I applied, it's much more c
On Wed 2017-09-06 19:54:52, Andy Lutomirski wrote:
> Patch 1 is the fix. Patch 2 is a comment that would have kept me from
> chasing down a false lead.
>
> I've tested patch 2 using CPU hotplug and suspend/resume. I haven't
> tested hibernation or kexec because I don't know how. (If I do
> syst
Hi!
> > Ok, seems this is still not completely right, I'm now getting WARN_ON
> > during boot and on every resume... but machine works.
> >
> > 4.14-rc0, 32-bit.
>
> Which SHA1, just to make sure? (Please enable CONFIG_LOCALVERSION_AUTO=y.)
>
> > [0.004000] Initializing CPU#1
> > [0.004
* Pavel Machek wrote:
> Hi!
>
> > * Pavel Machek wrote:
> >
> > > On Wed 2017-09-06 20:25:10, Linus Torvalds wrote:
> > > > On Wed, Sep 6, 2017 at 7:54 PM, Andy Lutomirski wrote:
> > > > > Patch 1 is the fix. Patch 2 is a comment that would have kept me from
> > > > > chasing down a false l
Hi!
> * Pavel Machek wrote:
>
> > On Wed 2017-09-06 20:25:10, Linus Torvalds wrote:
> > > On Wed, Sep 6, 2017 at 7:54 PM, Andy Lutomirski wrote:
> > > > Patch 1 is the fix. Patch 2 is a comment that would have kept me from
> > > > chasing down a false lead.
> > >
> > > Yes, this seems to fix
* Pavel Machek wrote:
> On Wed 2017-09-06 20:25:10, Linus Torvalds wrote:
> > On Wed, Sep 6, 2017 at 7:54 PM, Andy Lutomirski wrote:
> > > Patch 1 is the fix. Patch 2 is a comment that would have kept me from
> > > chasing down a false lead.
> >
> > Yes, this seems to fix things for me. Thank
On Wed 2017-09-06 20:25:10, Linus Torvalds wrote:
> On Wed, Sep 6, 2017 at 7:54 PM, Andy Lutomirski wrote:
> > Patch 1 is the fix. Patch 2 is a comment that would have kept me from
> > chasing down a false lead.
>
> Yes, this seems to fix things for me. Thanks.
>
> Of course, right now that lap
On Wed, Sep 06, 2017 at 07:54:52PM -0700, Andy Lutomirski wrote:
> Patch 1 is the fix. Patch 2 is a comment that would have kept me from
> chasing down a false lead.
>
> I've tested patch 2 using CPU hotplug and suspend/resume. I haven't
> tested hibernation or kexec because I don't know how. (
> On Sep 6, 2017, at 8:25 PM, Linus Torvalds
> wrote:
>
>> On Wed, Sep 6, 2017 at 7:54 PM, Andy Lutomirski wrote:
>> Patch 1 is the fix. Patch 2 is a comment that would have kept me from
>> chasing down a false lead.
>
> Yes, this seems to fix things for me. Thanks.
>
> Of course, right no
On Wed, Sep 6, 2017 at 7:54 PM, Andy Lutomirski wrote:
> Patch 1 is the fix. Patch 2 is a comment that would have kept me from
> chasing down a false lead.
Yes, this seems to fix things for me. Thanks.
Of course, right now that laptop has no working wifi with tip-of-tree
due to some issues with
Patch 1 is the fix. Patch 2 is a comment that would have kept me from
chasing down a false lead.
I've tested patch 2 using CPU hotplug and suspend/resume. I haven't
tested hibernation or kexec because I don't know how. (If I do
systemctl hibernate on my laptop, it happily writes out a hiberatio
13 matches
Mail list logo
