From: Mark Brown <broonie@kernel.org>
To: Wen Su <Wen.Su@mediatek.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Applied "regulator: mt6359: Add support for MT6359 regulator" to the regulator tree
Date: Mon, 2 Mar 2020 12:36:30 +0000 [thread overview]
Message-ID: <20200302123630.GB4166@sirena.org.uk> (raw)
In-Reply-To: <1583128432.18202.3.camel@mtkswgap22>
[-- Attachment #1: Type: text/plain, Size: 416 bytes --]
On Mon, Mar 02, 2020 at 01:53:52PM +0800, Wen Su wrote:
> On Wed, 2020-02-26 at 11:47 +0000, Mark Brown wrote:
> > ...and dropped because the MFD dependency isn't on a newly added driver
> > like it appeared.
> I am sorry to bother you. How should I proceed for this patch set which
> including regulator driver and MFD header file ? Please give advice.
It should be fine as is once the MFD bits are figured out.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-03-02 12:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 11:47 Applied "regulator: mt6359: Add support for MT6359 regulator" to the regulator tree Mark Brown
2020-03-02 5:53 ` Wen Su
2020-03-02 12:36 ` Mark Brown [this message]
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=20200302123630.GB4166@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Wen.Su@mediatek.com \
--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).