From: Sven Van Asbroeck <thesven73@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/4] regulator: tps6105x: add optional devicetree support
Date: Wed, 20 Nov 2019 09:15:24 -0500 [thread overview]
Message-ID: <CAGngYiV6iuNh5-mgmCx4RYOnWJAvDkwrpzEeonHf5oXfruqoRg@mail.gmail.com> (raw)
In-Reply-To: <20191119181426.GE3634@sirena.org.uk>
On Tue, Nov 19, 2019 at 1:14 PM Mark Brown <broonie@kernel.org> wrote:
>
> This and the binding look good. I think there's no interdependency with
> the other patches and I can just apply them?
PS I'm assuming you're accepting the regulator patch, so I'll remove it
from future versions of the patchset, and drop you from To: and Cc:,
to keep the noise down.
next prev parent reply other threads:[~2019-11-20 14:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 15:46 [PATCH v2 0/4] tps6105x add devicetree and leds support Sven Van Asbroeck
2019-11-19 15:46 ` [PATCH v2 1/4] tps6105x: add optional devicetree support Sven Van Asbroeck
2019-11-20 17:18 ` Applied "tps6105x: add optional devicetree support" to the regulator tree Mark Brown
2019-11-22 7:31 ` Lee Jones
2019-11-22 13:32 ` Mark Brown
2019-11-22 13:39 ` Sven Van Asbroeck
2019-11-22 14:42 ` Lee Jones
2019-11-19 15:46 ` [PATCH v2 2/4] regulator: tps6105x: add optional devicetree support Sven Van Asbroeck
2019-11-19 18:14 ` Mark Brown
2019-11-19 18:21 ` Sven Van Asbroeck
2019-11-20 14:15 ` Sven Van Asbroeck [this message]
2019-11-20 17:18 ` Applied "regulator: tps6105x: add optional devicetree support" to the regulator tree Mark Brown
2019-11-19 15:46 ` [PATCH v2 3/4] leds: tps6105x: add driver for mfd chip led mode Sven Van Asbroeck
2019-11-19 18:32 ` Dan Murphy
2019-11-19 18:59 ` Sven Van Asbroeck
2019-11-19 21:52 ` Sven Van Asbroeck
2019-11-19 15:46 ` [PATCH v2 4/4] dt-bindings: mfd: update TI tps6105x chip bindings Sven Van Asbroeck
2019-11-19 18:36 ` Dan Murphy
2019-11-19 19:03 ` Sven Van Asbroeck
2019-11-19 19:38 ` Jacek Anaszewski
2019-11-19 20:22 ` Sven Van Asbroeck
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=CAGngYiV6iuNh5-mgmCx4RYOnWJAvDkwrpzEeonHf5oXfruqoRg@mail.gmail.com \
--to=thesven73@gmail.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.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).