From: p.zabel@pengutronix.de (Philipp Zabel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/3] reset: Add support for shared reset controls
Date: Wed, 24 Feb 2016 11:42:37 +0100 [thread overview]
Message-ID: <1456310557.3396.34.camel@pengutronix.de> (raw)
In-Reply-To: <1456249586-12101-1-git-send-email-hdegoede@redhat.com>
Hi Hans,
Am Dienstag, den 23.02.2016, 18:46 +0100 schrieb Hans de Goede:
> Hi All,
>
> Here is v4 of my shared reset-controls patch.
>
> Changes in v3:
> -Rewrite as result of mailinglist discussions changing the API
Thank you, I have applied them with a small fixup on
git://git.pengutronix.de/git/pza/linux.git reset/next
best regards
Philipp
prev parent reply other threads:[~2016-02-24 10:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 17:46 [PATCH v4 0/3] reset: Add support for shared reset controls Hans de Goede
2016-02-23 17:46 ` [PATCH v4 1/3] reset: Make [of_]reset_control_get[_foo] functions wrappers Hans de Goede
2016-02-23 17:46 ` [PATCH v4 2/3] reset: Share struct reset_control between reset_control_get calls Hans de Goede
2016-02-23 17:46 ` [PATCH v4 3/3] reset: Add support for shared reset controls Hans de Goede
2016-02-24 10:42 ` Philipp Zabel [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=1456310557.3396.34.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--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 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).