linux-kernel - Re: [PATCH] regulator: core: do not report EPROBE

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: <20190417173028.GF5703@sirena.org.uk>
Date:   Wed, 17 Apr 2019 18:30:28 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Jorge Ramirez <jorge.ramirez-ortiz@...aro.org>
Cc:     lgirdwood@...il.com, linux-kernel@...r.kernel.org,
        khasim.mohammed@...aro.org
Subject: Re: [PATCH] regulator: core: do not report EPROBE_DEFER as error.

On Wed, Apr 17, 2019 at 07:05:52PM +0200, Jorge Ramirez wrote:
> On 4/17/19 17:46, Mark Brown wrote:

> > Please leave at least a debug log in place, it's not good to just
> > silently fail - even if we will retry someone might still need some help
> > debugging (eg, figuring out that they need to enable whatever driver is
> > providing the supply in their config) so we should tell them why we're
> > deferring.

> you mean replacing dev_err with dev_dbg on all cases or only on defer
> leaving  dev_err on the rest?

Only on defer.

> > BTW does an e-mail address need updating somewhere here?

> dont know, whose email? I got these from get_maintainer.pl (below); or
> are you referring to mine (in which case it is correct, I am back at
> least for a bit longer)

It was yours - you didn't show up in meet the team yet so I wasn't clear
if it was just an old patch where the e-mail address had been copied
over.

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