From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sebastian Reichel <sebastian.reichel@collabora.co.uk>
Cc: Evgeniy Polyakov <zbr@ioremap.net>,
Daniel Mack <daniel@zonque.org>,
robh+dt@kernel.org, mark.rutland@arm.com, szabolcs.gyurko@tlt.hu,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org, robert.jarzmik@free.fr
Subject: Re: [PATCH v4 3/5] w1: core: match sub-nodes of bus masters in devicetree
Date: Fri, 6 Jul 2018 16:51:33 +0200 [thread overview]
Message-ID: <20180706145133.GA8930@kroah.com> (raw)
In-Reply-To: <20180706135205.dkcrhbmaak2iteyw@earth.universe>
On Fri, Jul 06, 2018 at 03:52:05PM +0200, Sebastian Reichel wrote:
> Hi Greg & Evgeniy,
>
> I suggest, that I take this patch and the DT bindings together
> with the power-supply changes, once the bindings have been
> reviewed by Rob (Herring). I will prepare an immutable branch,
> that can be pulled into w1 as needed. Are you fine with this?
You can take it, no need to mess with me :)
greg k-h
next prev parent reply other threads:[~2018-07-06 14:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 5:35 [PATCH v4 0/5] Add devicetree functionality to w1 busses and ds2760 Daniel Mack
2018-07-06 5:35 ` [PATCH v4 1/5] dt-bindings: w1: document generic onewire bindings Daniel Mack
2018-07-11 15:01 ` Rob Herring
2018-07-18 12:40 ` Daniel Mack
2018-07-20 15:10 ` Rob Herring
2018-07-22 22:01 ` Sebastian Reichel
2018-07-06 5:35 ` [PATCH v4 2/5] dt-bindings: w1: document bindings for ds2760 battery monitor Daniel Mack
2018-07-11 15:02 ` Rob Herring
2018-07-06 5:35 ` [PATCH v4 3/5] w1: core: match sub-nodes of bus masters in devicetree Daniel Mack
2018-07-06 13:52 ` Sebastian Reichel
2018-07-06 14:51 ` Greg Kroah-Hartman [this message]
2018-07-06 5:35 ` [PATCH v4 4/5] power: supply: ds2760_battery: merge ds2760 supply driver with its w1 slave companion Daniel Mack
2018-07-06 13:36 ` Sebastian Reichel
2018-07-06 5:35 ` [PATCH v4 5/5] power: supply: ds2760_battery: add devicetree probing Daniel Mack
2018-07-06 13:43 ` Sebastian Reichel
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=20180706145133.GA8930@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=daniel@zonque.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robert.jarzmik@free.fr \
--cc=robh+dt@kernel.org \
--cc=sebastian.reichel@collabora.co.uk \
--cc=szabolcs.gyurko@tlt.hu \
--cc=zbr@ioremap.net \
/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.