From: John Crispin <john@phrozen.org>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Chen Zhong <chen.zhong@mediatek.com>,
John Crispin <blogic@openwrt.org>
Subject: Re: [PATCH V9 2/2] regulator: mt6323: Add support for MT6323 regulator
Date: Mon, 18 Jul 2016 14:19:08 +0200 [thread overview]
Message-ID: <2cfa2662-29af-5c9a-7e74-bdb0c22b83c3@phrozen.org> (raw)
In-Reply-To: <20160718121638.GT30372@sirena.org.uk>
On 18/07/2016 14:16, Mark Brown wrote:
> On Mon, Jul 18, 2016 at 02:09:01PM +0200, John Crispin wrote:
>
>> Changes in V9
>> * drop compatible string from devicetree
>
> Are you sure?
>
>> +static const struct of_device_id mt6323_of_match[] = {
>> + { .compatible = "mediatek,mt6323-regulator", },
>> + { /* sentinel */ },
>> +};
>> +MODULE_DEVICE_TABLE(of, mt6323_of_match);
>> +
>> +static struct platform_driver mt6323_regulator_driver = {
>> + .driver = {
>> + .name = "mt6323-regulator",
>> + .of_match_table = of_match_ptr(mt6323_of_match),
i was in the wrong folder while sending the patch so i ended up sending
the wrong patch with the wrong email account. sorry about the noise V10
coming up :/
next prev parent reply other threads:[~2016-07-18 12:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 12:09 [PATCH V9 1/2] regulator: Add document " John Crispin
2016-07-18 12:09 ` [PATCH V9 2/2] regulator: mt6323: Add support " John Crispin
2016-07-18 12:12 ` John Crispin
2016-07-18 12:16 ` Mark Brown
2016-07-18 12:19 ` John Crispin [this message]
2016-07-18 12:12 ` [PATCH V9 1/2] regulator: Add document " John Crispin
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=2cfa2662-29af-5c9a-7e74-bdb0c22b83c3@phrozen.org \
--to=john@phrozen.org \
--cc=blogic@openwrt.org \
--cc=broonie@kernel.org \
--cc=chen.zhong@mediatek.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.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
all inboxes | Powered by JetHome®