linux-kernel - Re: [PATCH v2 2/5] regulator: core: have regulator_dev_lookup() return ERR

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: <20170205144952.stprcykry2rszwun@sirena.org.uk>
Date:   Sun, 5 Feb 2017 15:49:52 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc:     Liam Girdwood <lgirdwood@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 2/5] regulator: core: have regulator_dev_lookup()
 return ERR_PTR-encoded errors

On Sat, Feb 04, 2017 at 10:19:21AM -0800, Dmitry Torokhov wrote:

> V2: replaced "return r ? r : ERR_PTR(-ENODEV);" with expanded "if"
> statement.

Please don't send new versions of patches as replies into the middle of
existing patch serieses, especially not by replying to individual
patches and even especially when bits of the earlier series have been
applied.  This just makes everything much more difficult to follow -
looking at an archive of the list it's hard to tell what the current
version of the series is and if old bits of the series aren't there the
numbering within the series you posted gets broken as there are missing
patches.

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