From: Mark Brown <broonie@kernel.org>
To: Michael Grzeschik <m.grzeschik@pengutronix.de>
Cc: linux-kernel@vger.kernel.org, kernel@pengutronix.de,
Philipp Zabel <p.zabel@pengutronix.de>
Subject: Re: [PATCH] regmap: irq: allow different device for irq chip and regmap
Date: Thu, 22 Jun 2017 11:33:47 +0100 [thread overview]
Message-ID: <20170622103347.yrdodqezeqtdmnpq@sirena.org.uk> (raw)
In-Reply-To: <20170622102617.13548-1-m.grzeschik@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 277 bytes --]
On Thu, Jun 22, 2017 at 12:26:17PM +0200, Michael Grzeschik wrote:
> same regmap.
>
> Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
> ---
All patches need to be signed off, please see SubmittingPatches for
details on what this means and why it's important.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2017-06-22 10:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 10:26 [PATCH] regmap: irq: allow different device for irq chip and regmap Michael Grzeschik
2017-06-22 10:33 ` Mark Brown [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=20170622103347.yrdodqezeqtdmnpq@sirena.org.uk \
--to=broonie@kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=m.grzeschik@pengutronix.de \
--cc=p.zabel@pengutronix.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).