netdev - Re: [PATCH net-next 16/20] can: rockchip_canfd: prepare to use full TX-FIFO depth

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <28a20a6697dbe610bd13829baa9d188ef22a1742.camel@googlemail.com>
Date: Wed, 04 Sep 2024 18:13:21 +0200
From: Christoph Fritz <chf.fritz@...glemail.com>
To: Marc Kleine-Budde <mkl@...gutronix.de>, netdev@...r.kernel.org
Cc: davem@...emloft.net, kuba@...nel.org, linux-can@...r.kernel.org, 
 kernel@...gutronix.de, Alibek Omarov <a1ba.omarov@...il.com>, Heiko
 Stuebner <heiko@...ech.de>
Subject: Re: [PATCH net-next 16/20] can: rockchip_canfd: prepare to use full
 TX-FIFO depth

> The workaround for the chips that are affected by erratum 6, i.e. EFF
> frames may be send as standard frames, is to re-send the EFF frame.
> This means the driver cannot queue the next frame for sending, as long
> ad the EFF frame has not been successfully send out.

just a nitpick, shouldn't it be "as" instead of "ad" ?