linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eduardo Valentin <edubezval@gmail.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: "rui.zhang" <rui.zhang@intel.com>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	Fabio Estevam <fabio.estevam@freescale.com>
Subject: Re: [PATCH] thermal: imx: Do not print error message in the EPROBE_DEFER case
Date: Fri, 12 Dec 2014 09:13:25 -0400	[thread overview]
Message-ID: <20141212131323.GB19853@developer> (raw)
In-Reply-To: <CAOMZO5Ao2=wbKj4VtU4bq5FhMfeOaMW5M9kmjf7y7o0vx-WJDA@mail.gmail.com>

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

Fabio,

On Thu, Dec 11, 2014 at 09:18:25PM -0200, Fabio Estevam wrote:
> Hi Eduardo,
> 
> On Thu, Dec 11, 2014 at 9:14 PM, Eduardo Valentin <edubezval@gmail.com> wrote:
> 
> > Thanks for your patch. But I am queuing a different patch that does a
> > similar job.
> >
> > https://git.kernel.org/cgit/linux/kernel/git/evalenti/linux-soc-thermal.git/commit/?h=fixes&id=0f1be51c358f740fe5183bd0bcd60076fdfb53d0
> 
> I am running linux-next 20141211, which has this commit applied.
> 
> > Can you please check my -fixes branch? When EPROBE_DEFER happens, we are
> > now printing a debug message only.
> 
> On linux-next I am still getting the error, so I still needed my patch.

Understood. I will be queuing it in my -fixes branch.

Thanks!

> 
> Thanks

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

      reply	other threads:[~2014-12-12 13:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-11 21:11 [PATCH] thermal: imx: Do not print error message in the EPROBE_DEFER case Fabio Estevam
2014-12-11 23:14 ` Eduardo Valentin
2014-12-11 23:18   ` Fabio Estevam
2014-12-12 13:13     ` Eduardo Valentin [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=20141212131323.GB19853@developer \
    --to=edubezval@gmail.com \
    --cc=fabio.estevam@freescale.com \
    --cc=festevam@gmail.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=rui.zhang@intel.com \
    /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).