From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: linux-kernel@vger.kernel.org, Wolfram Sang <wsa@the-dreams.de>,
Chen-Yu Tsai <wens@csie.org>,
"Ivan T. Ivanov" <iivanov@mm-sol.com>,
Barry Song <Baohua.Song@csr.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Pavel Machek <pavel@ucw.cz>, Shawn Guo <shawn.guo@linaro.org>,
Marek Vasut <marex@denx.de>, Stephen Warren <swarren@nvidia.com>,
kernel@pengutronix.de
Subject: Re: [PATCH] reset: Add optional resets and stubs
Date: Fri, 7 Mar 2014 18:57:14 +0100 [thread overview]
Message-ID: <20140307175714.GX607@lukather> (raw)
In-Reply-To: <1394202623-20229-1-git-send-email-p.zabel@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 763 bytes --]
Hi Philipp,
On Fri, Mar 07, 2014 at 03:30:23PM +0100, Philipp Zabel wrote:
> This patch adds device_reset_optional and (devm_)reset_control_get_optional
> variants that drivers can use to indicate they can function without control
> over the reset line. For those functions, stubs are added so the drivers can
> be compiled with CONFIG_RESET_CONTROLLER disabled.
> Also, device_reset is annotated with __must_check. Drivers ignoring the return
> value should use device_reset_optional instead.
>
> Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
Reviewed-by: Maxime Ripard <maxime.ripard@free-electrons.com>
Thanks!
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-03-07 18:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 14:30 [PATCH] reset: Add optional resets and stubs Philipp Zabel
2014-03-07 15:39 ` Wolfram Sang
2014-03-07 17:06 ` Philipp Zabel
2014-03-07 17:57 ` Maxime Ripard [this message]
2014-03-08 11:38 ` Marek Vasut
2014-03-08 22:34 ` Wolfram Sang
2014-03-10 9:39 ` Ivan T. Ivanov
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=20140307175714.GX607@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=Baohua.Song@csr.com \
--cc=iivanov@mm-sol.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=p.zabel@pengutronix.de \
--cc=pavel@ucw.cz \
--cc=shawn.guo@linaro.org \
--cc=swarren@nvidia.com \
--cc=swarren@wwwdotorg.org \
--cc=wens@csie.org \
--cc=wsa@the-dreams.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 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.