lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Mon, 29 Apr 2019 08:53:19 +0000
From:   Rasmus Villemoes <rasmus.villemoes@...vas.dk>
To:     Marc Kleine-Budde <mkl@...gutronix.de>,
        Wolfgang Grandegger <wg@...ndegger.com>,
        "David S. Miller" <davem@...emloft.net>
CC:     Thomas Winding <twi@...f.com>, Fabio Estevam <festevam@...il.com>,
        Per Christensen <pnc@...f.com>,
        Rasmus Villemoes <Rasmus.Villemoes@...vas.se>,
        "linux-can@...r.kernel.org" <linux-can@...r.kernel.org>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Joakim Zhang <qiangqing.zhang@....com>
Subject: Re: [PATCH] can: flexcan: bump FLEXCAN_TIMEOUT_US to 250

On 22/03/2019 08.51, Marc Kleine-Budde wrote:
> On 3/22/19 8:45 AM, Rasmus Villemoes wrote:
>> On 21/03/2019 16.30, Marc Kleine-Budde wrote:
>>> On 3/21/19 3:34 PM, Rasmus Villemoes wrote:
>>>> On 20/03/2019 14.18, Marc Kleine-Budde wrote:
>>>
>>> Can you propose an updated commit message for Joakim Zhang's patch?
>>>
>>> https://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can.git/commit/?h=testing&id=9daed89ae8a3fc44ccd2b2bb9c3c4d3e3431904d
>>>
>>> I'll add it by hand and increase the timeout to 250. Ok?
>>
>> Sounds fine. In order not to change Joakim's commit log too much, how
>> about adding something like (with your initials, since you're next in
>> the sign-off chain)
>>
>> [mkl: Meanwhile, Rasmus Villemoes reported that even with a timeout of
>> 100, flexcan_probe() fails on the MPC8309, which requires a value of at
>> least 140 to work reliably. 250 works for everyone.]
>>
>> ? Feel free to edit as you wish.
> 
> Thanks, I've added that to the commit message itself.

What's the status of this? I can't find anything in -next (as of
next-20190426), neither Joakim's original or the amended patch.

Thanks,
Rasmus

Powered by blists - more mailing lists