[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c5918fa9-ec37-9636-5230-57260f7e8427@cambridgegreys.com>
Date: Fri, 10 May 2019 17:22:18 +0100
From: Anton Ivanov <anton.ivanov@...bridgegreys.com>
To: Bartosz Golaszewski <brgl@...ev.pl>,
Richard Weinberger <richard@....at>
Cc: Richard Weinberger <richard.weinberger@...il.com>,
Jeff Dike <jdike@...toit.com>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
Bartosz Golaszewski <bgolaszewski@...libre.com>,
linux-um@...ts.infradead.org,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [RESEND PATCH 4/4] um: irq: don't set the chip for all irqs
On 10/05/2019 17:20, Bartosz Golaszewski wrote:
> pt., 10 maj 2019 o 11:16 Bartosz Golaszewski <brgl@...ev.pl> napisał(a):
>> śr., 8 maj 2019 o 09:13 Richard Weinberger <richard@....at> napisał(a):
>>> ----- Ursprüngliche Mail -----
>>>>> Can you please check?
>>>>> This patch is already queued in -next. So we need to decide whether to
>>>>> revert or fix it now.
>>>>>
>>>> I am looking at it. It passed tests in my case (I did the usual round).
>>> It works here too. That's why I never noticed.
>>> Yesterday I noticed just because I looked for something else in the kernel logs.
>>>
>>> Thanks,
>>> //richard
>> Hi,
>>
>> sorry for the late reply - I just came back from vacation.
>>
>> I see it here too, I'll check if I can find the culprit and fix it today.
>>
>> Bart
> Hi Richard, Anton,
>
> I'm not sure yet what this is caused by. It doesn't seem to break
> anything for me but since it's a new error message I guess it's best
> to revert this patch (others are good) and revisit it for v5.3.
Can you send me your command line and .config so I can try to reproduce it.
Brgds,
>
> Bart
>
--
Anton R. Ivanov
Cambridgegreys Limited. Registered in England. Company Number 10273661
https://www.cambridgegreys.com/
Powered by blists - more mailing lists