From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] backlight: Fix broken regulator API usage in l4f00242t03
Date: Mon, 15 Aug 2011 13:06:22 +0000 [thread overview]
Message-ID: <20110815130619.GB3927@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20110815064242.GR31404@pengutronix.de>
On Mon, Aug 15, 2011 at 08:42:42AM +0200, Sascha Hauer wrote:
> Maybe you could change these pr_err to dev_err on the way. The rest of
> the driver already uses dev_*.
Minimal diff and all that...
WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] backlight: Fix broken regulator API usage in l4f00242t03
Date: Mon, 15 Aug 2011 22:06:22 +0900 [thread overview]
Message-ID: <20110815130619.GB3927@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20110815064242.GR31404@pengutronix.de>
On Mon, Aug 15, 2011 at 08:42:42AM +0200, Sascha Hauer wrote:
> Maybe you could change these pr_err to dev_err on the way. The rest of
> the driver already uses dev_*.
Minimal diff and all that...
next prev parent reply other threads:[~2011-08-15 13:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-15 1:41 [PATCH] backlight: Fix broken regulator API usage in l4f00242t03 Mark Brown
2011-08-15 1:41 ` Mark Brown
2011-08-15 6:42 ` Sascha Hauer
2011-08-15 6:42 ` Sascha Hauer
2011-08-15 13:06 ` Mark Brown [this message]
2011-08-15 13:06 ` Mark Brown
2011-08-15 15:48 ` Sascha Hauer
2011-08-15 15:48 ` Sascha Hauer
2011-08-15 14:50 ` Mark Brown
2011-08-15 14:50 ` Mark Brown
2011-08-19 3:50 ` Fabio Estevam
2011-08-19 3:50 ` Fabio Estevam
-- strict thread matches above, loose matches on Subject: below --
2011-09-05 18:10 Mark Brown
2011-09-06 3:58 ` Florian Tobias Schandinat
2011-09-06 5:45 ` Mark Brown
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=20110815130619.GB3927@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.