linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Jorge Ramirez <jorge.ramirez-ortiz@linaro.org>
Cc: lgirdwood@gmail.com, linux-kernel@vger.kernel.org,
	khasim.mohammed@linaro.org
Subject: Re: [PATCH] regulator: core: do not report EPROBE_DEFER as error.
Date: Wed, 17 Apr 2019 18:30:28 +0100	[thread overview]
Message-ID: <20190417173028.GF5703@sirena.org.uk> (raw)
In-Reply-To: <7d84d820-c3e9-16cb-b5b7-31761589d4ec@linaro.org>

[-- Attachment #1: Type: text/plain, Size: 918 bytes --]

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.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2019-04-17 17:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-17  8:54 [PATCH] regulator: core: do not report EPROBE_DEFER as error Jorge Ramirez-Ortiz
2019-04-17 15:46 ` Mark Brown
2019-04-17 17:05   ` Jorge Ramirez
2019-04-17 17:30     ` Mark Brown [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190417173028.GF5703@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=jorge.ramirez-ortiz@linaro.org \
    --cc=khasim.mohammed@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).