linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, Lars-Peter Clausen <lars@metafoo.de>,
	Thierry Reding <thierry.reding@avionic-design.de>,
	kernel@pengutronix.de
Subject: Re: [PATCH v3] input: pwm-beeper: Add devicetree probing support
Date: Sat, 3 Nov 2012 22:33:40 +0100	[thread overview]
Message-ID: <20121103213340.GS1641@pengutronix.de> (raw)
In-Reply-To: <20121103190301.GB11349@core.coreip.homeip.net>

Hi Dmitry,

On Sat, Nov 03, 2012 at 12:03:01PM -0700, Dmitry Torokhov wrote:
> Hi Sascha.
> 
> On Fri, Nov 02, 2012 at 09:44:02AM +0100, Sascha Hauer wrote:
> >  
> > -	beeper->pwm = pwm_request(pwm_id, "pwm beeper");
> > +	beeper->pwm = pwm_get(&pdev->dev, NULL);
> > +	if (IS_ERR(beeper->pwm)) {
> > +		dev_err(&pdev->dev, "unable to request PWM, trying legacy API\n");
> 
> This is not an error, I'll switch it over to dev_dbg().

This is cut and paste from some other driver. I suppose it's dev_err to
motivate people to update their boards. Anyway, dev_dbg is fine with me.

Thanks,
 Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

      reply	other threads:[~2012-11-03 21:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-02  8:44 [PATCH v3] input: pwm-beeper: Add devicetree probing support Sascha Hauer
2012-11-02  9:10 ` Thierry Reding
2012-11-03 19:03 ` Dmitry Torokhov
2012-11-03 21:33   ` Sascha Hauer [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=20121103213340.GS1641@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=dmitry.torokhov@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=lars@metafoo.de \
    --cc=linux-input@vger.kernel.org \
    --cc=thierry.reding@avionic-design.de \
    /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).