From: Tim Harvey <tharvey@gateworks.com>
To: Rob Herring <robh@kernel.org>
Cc: Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Jaffer Kapasi <jkapasi@linear.com>
Subject: Re: [PATCH] regulator: Add LTC3676 support
Date: Wed, 10 Aug 2016 17:46:44 -0700 [thread overview]
Message-ID: <CAJ+vNU2UjYUzMS+yipc-gZM0a2=9inrmTX_qnMQ5JD9c4xpzvw@mail.gmail.com> (raw)
In-Reply-To: <20160810222825.GA2650@rob-hp-laptop>
On Wed, Aug 10, 2016 at 3:28 PM, Rob Herring <robh@kernel.org> wrote:
> On Tue, Aug 09, 2016 at 04:36:07PM -0700, Tim Harvey wrote:
>> This patch adds support for the Linear Technology LTC3676
>> 8-output I2C voltage regulator IC.
>>
>> Cc: Jaffer Kapasi <jkapasi@linear.com>
>> Signed-off-by: Tim Harvey <tharvey@gateworks.com>
>> ---
>> .../devicetree/bindings/regulator/ltc3676.txt | 94 ++++
>
> Acked-by: Rob Herring <robh@kernel.org>
>
Rob,
Should I have submitted this as a two patch series so that I could add
your 'Acked-by' for that patch or is there a standard way for me to
add your 'Acked-by' to future versions of the patch 'just' for that
particular file?
Regards,
Tim
next prev parent reply other threads:[~2016-08-11 0:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 23:36 [PATCH] regulator: Add LTC3676 support Tim Harvey
2016-08-10 11:41 ` Mark Brown
2016-08-11 0:44 ` Tim Harvey
2016-08-11 9:45 ` Mark Brown
2016-08-11 20:48 ` Tim Harvey
2016-08-12 9:21 ` Mark Brown
2016-08-10 22:28 ` Rob Herring
2016-08-11 0:46 ` Tim Harvey [this message]
2016-08-15 19:40 ` [PATCH v2] " Tim Harvey
2016-08-16 11:30 ` Applied "regulator: Add LTC3676 support" to the regulator tree Mark Brown
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='CAJ+vNU2UjYUzMS+yipc-gZM0a2=9inrmTX_qnMQ5JD9c4xpzvw@mail.gmail.com' \
--to=tharvey@gateworks.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jkapasi@linear.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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).