On 5/31/19 7:02 PM, Jon Maloy wrote:
> This was the very reason the broken patch was introduced. AFAIK there is no
> problem after the corrected version of that patch was applied.
I have prepared for our patches on net-next tree. But when I checked my
patches on net tree, it's found that the issu
> -Original Message-
> From: Ying Xue
> Sent: 30-May-19 20:41
> To: Mihai Moldovan ; Jon Maloy
> ; linux-kernel@vger.kernel.org
> Subject: Re: Userspace woes with 5.1.5 due to TIPC
>
> On 5/31/19 4:47 AM, Mihai Moldovan wrote:
> > * On 5/30/19 9:51 PM, J
On 5/31/19 4:47 AM, Mihai Moldovan wrote:
> * On 5/30/19 9:51 PM, Jon Maloy wrote:
>> Make sure the following three commits are present in TIPC *after* the
>> offending commit:
>>
>> commit 532b0f7ece4c "tipc: fix modprobe tipc failed after switch order of
>> device registration"
>
> This *is* t
* On 5/30/19 9:51 PM, Jon Maloy wrote:
> Make sure the following three commits are present in TIPC *after* the
> offending commit:
>
> commit 532b0f7ece4c "tipc: fix modprobe tipc failed after switch order of
> device registration"
This *is* the offending commit, as far as I understand. Merely
Hi Mihai,
Make sure the following three commits are present in TIPC *after* the offending
commit:
commit 532b0f7ece4c "tipc: fix modprobe tipc failed after switch order of
device registration"
Since that patch one was flawed it had to be reverted:
commit 5593530e5694 ""Revert tipc: fix modprob
5 matches
Mail list logo
