linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Iskren Chernev <iskren.chernev@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
	Andy Gross <agross@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
	phone-devel@vger.kernel.org,
	~postmarketos/upstreaming@lists.sr.ht
Subject: Re: [RFC PATCH 2/2] regulator: qcom_smd: Add PM6125 regulator support
Date: Fri, 3 Sep 2021 22:49:52 +0300	[thread overview]
Message-ID: <b02e3ba5-b3fe-8963-8457-62304a39e100@gmail.com> (raw)
In-Reply-To: <20210903152331.GK4932@sirena.org.uk>



On 9/3/21 6:23 PM, Mark Brown wrote:
> On Sat, Aug 28, 2021 at 02:56:54PM +0300, Iskren Chernev wrote:
> 
>> NOTE: The sources haven't been determined, so currently each regulator
>> has it's own source.
> 
> It would probably be safer to just leave them unspecified for now and
> then add them as people figure out what's going on rather than putting
> something incorrect into the DT bindings.

I didn't expect this patch to be mergeable, so I didn't add the dt-bindings.

So should I add bindings and just ignore all the sources (add them later)?

Regards,
Iskren

  reply	other threads:[~2021-09-03 19:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-28 11:56 [RFC PATCH 0/2] PM6125 regulator support Iskren Chernev
2021-08-28 11:56 ` [RFC PATCH 1/2] regulator: qcom_spmi: Add PM6125 regulators Iskren Chernev
2021-08-28 11:56 ` [RFC PATCH 2/2] regulator: qcom_smd: Add PM6125 regulator support Iskren Chernev
2021-09-03 15:23   ` Mark Brown
2021-09-03 19:49     ` Iskren Chernev [this message]
2021-09-13 14:32       ` Mark Brown
2021-09-03 15:24 ` [RFC PATCH 0/2] " 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=b02e3ba5-b3fe-8963-8457-62304a39e100@gmail.com \
    --to=iskren.chernev@gmail.com \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phone-devel@vger.kernel.org \
    --cc=~postmarketos/upstreaming@lists.sr.ht \
    /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).