From: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>
To: Keerthy <j-keerthy@ti.com>
Cc: linux-kernel@vger.kernel.org, Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org
Subject: Re: [PATCH 1/2] regulator: tps65910: check TPS65910_NUM_REGS at build time
Date: Tue, 13 Jun 2017 16:35:54 +0200 [thread overview]
Message-ID: <20170613143554.vvysqw2pjql4n6jm@qmqm.qmqm.pl> (raw)
In-Reply-To: <8d9e234b-8963-8ee8-8330-cfbe04f4a119@ti.com>
On Tue, Jun 13, 2017 at 07:31:21PM +0530, Keerthy wrote:
> On Tuesday 13 June 2017 07:28 PM, Michał Mirosław wrote:
>
> Missing commit log?
[...]
Oh, indeed. I'll fix this in a moment.
Best Regards,
Michał Mirosław
next prev parent reply other threads:[~2017-06-13 14:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 13:58 [PATCH 1/2] regulator: tps65910: check TPS65910_NUM_REGS at build time Michał Mirosław
2017-06-13 13:58 ` [PATCH 2/2] regulator: tps65910: Allow supply references to the same chip Michał Mirosław
2017-06-13 14:01 ` [PATCH 1/2] regulator: tps65910: check TPS65910_NUM_REGS at build time Keerthy
2017-06-13 14:35 ` Michał Mirosław [this message]
2017-06-13 14:41 ` [PATCH v2 " Michał Mirosław
2017-06-13 14:41 ` [PATCH v2 2/2] regulator: tps65910: Allow supply references to the same chip Michał Mirosław
2017-06-13 17:46 ` Mark Brown
2017-06-13 20:22 ` Michał Mirosław
2017-06-13 20:42 ` Mark Brown
2017-06-14 7:56 ` Javier Martinez Canillas
2017-06-14 12:14 ` Michał Mirosław
2017-06-13 17:44 ` [PATCH v2 1/2] regulator: tps65910: check TPS65910_NUM_REGS at build time 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=20170613143554.vvysqw2pjql4n6jm@qmqm.qmqm.pl \
--to=mirq-linux@rere.qmqm.pl \
--cc=broonie@kernel.org \
--cc=j-keerthy@ti.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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).