From: Philipp Zabel <p.zabel@pengutronix.de>
To: Peter Rosin <peda@axentia.se>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Sakari Ailus <sakari.ailus@iki.fi>,
Steve Longerbeam <slongerbeam@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@pengutronix.de
Subject: Re: [RFC v3 2/2] mux: mmio-based syscon mux controller
Date: Mon, 08 May 2017 10:12:24 +0200 [thread overview]
Message-ID: <1494231144.3029.25.camel@pengutronix.de> (raw)
In-Reply-To: <f43fe769-426f-2bfe-fb58-c69743171b0d@axentia.se>
Hi Peter,
On Mon, 2017-05-08 at 10:00 +0200, Peter Rosin wrote:
> Hi Philipp,
>
> With the ack on the bindings in place, I'm going to pile these
> two patches on top of my mux series when I send v15 next week (or
> whenever v4.12-rc1 is out). There are a pair of nitpicks that I'm
> going to fix myself, so no need for a resend.
Yes, please. While at it, could you also fix my "bitfieldis" typo in the
commit description of patch 1.
> Thank you very much for making use of the new code, I hope the
> "3rd party interest" will help getting the mux series merged...
Thanks to Sakari for pointing it out in the video-mux review.
regards
Philipp
next prev parent reply other threads:[~2017-05-08 8:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 11:52 [RFC v3 1/2] dt-bindings: add mmio-based syscon mux controller DT bindings Philipp Zabel
2017-04-28 11:52 ` [RFC v3 2/2] mux: mmio-based syscon mux controller Philipp Zabel
2017-05-08 8:00 ` Peter Rosin
2017-05-08 8:12 ` Philipp Zabel [this message]
[not found] ` <1494231144.3029.25.camel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2017-05-08 8:38 ` Peter Rosin
[not found] ` <1493380324-20638-1-git-send-email-p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2017-05-05 19:55 ` [RFC v3 1/2] dt-bindings: add mmio-based syscon mux controller DT bindings Rob Herring
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=1494231144.3029.25.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=peda@axentia.se \
--cc=robh+dt@kernel.org \
--cc=sakari.ailus@iki.fi \
--cc=slongerbeam@gmail.com \
/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).