linux-kernel - Re: [PATCH v2] spi: spidev: Add compatible for LWE's btt device

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: <5f514949-5162-4944-8424-bf19318c5611@sirena.org.uk>
Date: Wed, 26 Mar 2025 18:06:52 +0000
From: Mark Brown <broonie@...nel.org>
To: Lukasz Majewski <lukma@...x.de>
Cc: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] spi: spidev: Add compatible for LWE's btt device

On Wed, Mar 26, 2025 at 06:45:53PM +0100, Lukasz Majewski wrote:
> > On Wed, Mar 26, 2025 at 06:24:45PM +0100, Lukasz Majewski wrote:

> > Note also that as previously mentioned I expect to see a binding
> > document update too which doesn't appear to be here.

> I've just send it to be accepted to trivial-devices.yaml

As previously mentioned you should send the bindings update along with
the driver code.

> > Please don't send new patches in reply to old patches or serieses,
> > this makes it harder for both people and tools to understand what is
> > going on - it can bury things in mailboxes and make it difficult to
> > keep track of what current patches are, both for the new patches and
> > the old ones.

> Ok, I thought that it would be the opposite - that you would see v2 as
> the reply to the old one - especially that the change is just a single
> letter.

That's exactly the problem.

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