From: Felipe Balbi <balbi@ti.com>
To: Fabio Baltieri <fabio.baltieri@linaro.org>
Cc: Felipe Balbi <balbi@ti.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
<linux-kernel@vger.kernel.org>, <linux-usb@vger.kernel.org>
Subject: Re: [PATCH 0/3] check regulator_enable() return value
Date: Wed, 3 Apr 2013 17:06:22 +0300 [thread overview]
Message-ID: <20130403140622.GI14680@arwen.pp.htv.fi> (raw)
In-Reply-To: <1364997747-20830-1-git-send-email-fabio.baltieri@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 607 bytes --]
Hi,
On Wed, Apr 03, 2013 at 04:02:24PM +0200, Fabio Baltieri wrote:
> While testing your 'next' branch merged with today's next I got some new
> warnings, caused by a recently introduced __must_check in:
>
> c8801a8 regulator: core: Mark all get and enable calls as __must_check
>
> These patches introduces a check for regulator_enable() return value in
> all three affected USB phy drivers, and issue a dev_err() in case it
> fails.
>
> TWL4030 and TWL6030 patches has been build-tested only.
Sorry but I can't change my tree anymore, we can send these during
v3.10-rc.
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-04-03 14:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-03 14:02 [PATCH 0/3] check regulator_enable() return value Fabio Baltieri
2013-04-03 14:02 ` [PATCH 1/3] usb: phy: ab8500-usb: check regulator_enable " Fabio Baltieri
2013-04-03 14:02 ` [PATCH 2/3] usb: phy: twl4030-usb: " Fabio Baltieri
2013-04-03 15:12 ` Kalle Jokiniemi
2013-04-03 14:02 ` [PATCH 3/3] usb: phy: twl6030-usb: " Fabio Baltieri
2013-04-03 14:06 ` Felipe Balbi [this message]
2013-04-03 14:12 ` [PATCH 0/3] check regulator_enable() " Fabio Baltieri
2013-04-03 14:22 ` Greg KH
2013-04-03 15:44 ` Felipe Balbi
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=20130403140622.GI14680@arwen.pp.htv.fi \
--to=balbi@ti.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=fabio.baltieri@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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