All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jisheng Zhang <Jisheng.Zhang@synaptics.com>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	Saravanan Sekar <sravanhome@gmail.com>,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3 1/4] regulator: mp886x: implement set_ramp_delay
Date: Fri, 21 Aug 2020 10:17:29 +0800	[thread overview]
Message-ID: <20200821101729.76f1951b@xhacker.debian> (raw)
In-Reply-To: <20200820210513.GA41191@sirena.org.uk>

On Thu, 20 Aug 2020 22:05:13 +0100 Mark Brown wrote:

> On Thu, Aug 20, 2020 at 05:10:51PM +0800, Jisheng Zhang wrote:
> > Implement the .set_ramp_delay for MP8867 and MP8869. MP8867 and MP8869
> > could share the implementation, the only difference is the slew_rates
> > array.  
> 
> This doesn't apply against current code, please check and resend.

I found the reason, the three patches in v2 were applied to for-next tree.
Should I renew patches based on for-next? Since the "mps,switch-frequency"
binding isn't released and used, I think I can send new patches to convert
mps,switch-frequency to mps,switch-frequency-hz.

Thanks

  reply	other threads:[~2020-08-21  2:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-20  9:10 [PATCH v3 0/4] regulator: mp886x: two features and dt json convert Jisheng Zhang
2020-08-20  9:10 ` [PATCH v3 1/4] regulator: mp886x: implement set_ramp_delay Jisheng Zhang
2020-08-20 21:05   ` Mark Brown
2020-08-21  2:17     ` Jisheng Zhang [this message]
2020-08-21  9:57       ` Mark Brown
2020-08-20  9:11 ` [PATCH v3 2/4] dt-bindings: regulator: mp886x: support mps,switch-frequency-hz Jisheng Zhang
2020-08-20  9:11 ` [PATCH v3 3/4] regulator: mp886x: support setting switch freq Jisheng Zhang
2020-08-20  9:12 ` [PATCH v3 4/4] dt-bindings: regulator: Convert mp886x to json-schema Jisheng Zhang

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=20200821101729.76f1951b@xhacker.debian \
    --to=jisheng.zhang@synaptics.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=sravanhome@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.