From: Dan Murphy <dmurphy@ti.com>
To: Mark Brown <broonie@kernel.org>
Cc: <jacek.anaszewski@gmail.com>, <pavel@ucw.cz>,
<lgirdwood@gmail.com>, <lee.jones@linaro.org>,
<linux-leds@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 1/6] regulator: lm363x: Make the gpio register enable flexible
Date: Wed, 5 Jun 2019 11:32:02 -0500 [thread overview]
Message-ID: <c01c0177-6f28-dc2a-bae7-a5d18c30ce5d@ti.com> (raw)
In-Reply-To: <20190605163120.GR2456@sirena.org.uk>
Mark
On 6/5/19 11:31 AM, Mark Brown wrote:
> On Wed, Jun 05, 2019 at 07:47:50AM -0500, Dan Murphy wrote:
>> On 6/5/19 7:02 AM, Dan Murphy wrote:
>>> I can squash patch 1 into 4.
>>> Also not sure what you mean by new validation.
>> Disregard I understand. The patch is missing the validation code.
> Ah, some git add issues I guess :) Squashing would help but it's not
> essential I think.
More like PEBKAC on this one
Dan
next prev parent reply other threads:[~2019-06-05 16:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 17:43 [PATCH v5 0/6] LM36274 Introduction Dan Murphy
2019-06-04 17:43 ` [PATCH v5 1/6] regulator: lm363x: Make the gpio register enable flexible Dan Murphy
2019-06-05 10:01 ` Mark Brown
2019-06-05 12:02 ` Dan Murphy
2019-06-05 12:47 ` Dan Murphy
2019-06-05 16:31 ` Mark Brown
2019-06-05 16:32 ` Dan Murphy [this message]
2019-06-06 9:47 ` Pavel Machek
2019-06-04 17:43 ` [PATCH v5 2/6] dt-bindings: mfd: Add lm36274 bindings to ti-lmu Dan Murphy
2019-06-06 9:49 ` Pavel Machek
2019-06-04 17:43 ` [PATCH v5 3/6] mfd: ti-lmu: Add LM36274 support to the ti-lmu Dan Murphy
2019-06-04 17:43 ` [PATCH v5 4/6] regulator: lm363x: Add support for LM36274 Dan Murphy
2019-06-04 17:43 ` [PATCH v5 5/6] dt-bindings: leds: Add LED bindings for the LM36274 Dan Murphy
2019-06-04 17:43 ` [PATCH v5 6/6] leds: lm36274: Introduce the TI LM36274 LED driver Dan Murphy
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=c01c0177-6f28-dc2a-bae7-a5d18c30ce5d@ti.com \
--to=dmurphy@ti.com \
--cc=broonie@kernel.org \
--cc=jacek.anaszewski@gmail.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
/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
all inboxes | Powered by JetHome®