linux-kernel - Re: [RFC PATCH] i2c: rcar: bring hardware to known state when probing

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]

Message-ID: <ZoZyGzMquiIMwAni@shikoro>
Date: Thu, 4 Jul 2024 11:57:47 +0200
From: Wolfram Sang <wsa+renesas@...g-engineering.com>
To: Andi Shyti <andi.shyti@...nel.org>
Cc: linux-renesas-soc@...r.kernel.org, Dirk Behme <dirk.behme@...bosch.com>,
	Geert Uytterhoeven <geert+renesas@...der.be>,
	linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH] i2c: rcar: bring hardware to known state when probing


> Do we need the Fixes tag here?

We can add the initial commit for this driver. That means the commit
message is wrong because refactorization is not the culprit. So, I will
resend with Fixes-tag and updated commit message.

> Looks reasonable. If testing is fine I can queue this up for this
> week's pull request.

First testing looks good. I will do some more.


Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)