linux-kernel - Re: linux-next: manual merge of the spi tree with the i2c tree

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: <Y/T5tevqPapMy/g6@sirena.org.uk>
Date:   Tue, 21 Feb 2023 17:04:53 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Wolfram Sang <wsa@...-dreams.de>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        Geert Uytterhoeven <geert@...ux-m68k.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Wolfram Sang <wsa@...nel.org>
Subject: Re: linux-next: manual merge of the spi tree with the i2c tree

On Tue, Feb 21, 2023 at 05:57:41PM +0100, Alain Volmat wrote:

> should I update something to avoid this conflict before you push the
> pull request for v6.3 ?

No, it's fine.

Please don't top post, reply in line with needed context.  This allows
readers to readily follow the flow of conversation and understand what
you are talking about and also helps ensure that everything in the
discussion is being addressed.

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