linux-kernel - Re: [PATCH] regmap: regmap-w1: Fix build troubles

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: <20170710103141.teuhsi7o3b4grxjw@sirena.org.uk>
Date:   Mon, 10 Jul 2017 11:31:41 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Sebastian Reichel <sebastian.reichel@...labora.co.uk>
Cc:     "Alex A. Mihaylov" <minimumlaw@...bler.ru>,
        Evgeniy Polyakov <zbr@...emap.net>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] regmap: regmap-w1: Fix build troubles

On Sat, Jul 08, 2017 at 04:58:08PM +0200, Sebastian Reichel wrote:
> On Fri, Jul 07, 2017 at 06:38:22PM +0300, Alex A. Mihaylov wrote:
> > Fixes: cc5d0db390b0 ("regmap: Add 1-Wire bus support")
> > Commit de0d6dbdbdb2 ("w1: Add subsystem kernel public interface")
> > Fix place off w1.h header file

> > Cosmetic: Fix company name (local to international)

> > Signed-off-by: Alex A. Mihaylov <minimumlaw@...bler.ru>

> This should go into 4.13, but you actually did not include the
> maintainer of regmap (which I just added, but you may have to
> resend the patch, so that it lands in his inbox). Anyways the
> change is:

No, he sent it to me originally and I redirected him to whoever has
moved the header file - the regmap code is in Linus' tree already, if
the header file is going to be moved this needs to include the regmap
support and this patch.  I did at the time provide a signed tag for the
regmap 1wire support for precisely this purpose :(

Patches like this *really* shouldn't be appearing during the merge
window, they should be being handled well before that with everything
ready in -next when the merge window opens.

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