All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: saravanan sekar <sravanhome@gmail.com>
Cc: lgirdwood@gmail.com, robh+dt@kernel.org, mark.rutland@arm.com,
	mripard@kernel.org, shawnguo@kernel.org, heiko@sntech.de,
	sam@ravnborg.org, icenowy@aosc.io,
	laurent.pinchart@ideasonboard.com, gregkh@linuxfoundation.org,
	Jonathan.Cameron@huawei.com, davem@davemloft.net,
	mchehab+samsung@kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 3/4] regulator: mpq7920: add mpq7920 regulator driver
Date: Thu, 9 Jan 2020 19:16:54 +0000	[thread overview]
Message-ID: <20200109191654.GC3702@sirena.org.uk> (raw)
In-Reply-To: <aefe7c78-6bd9-bafd-9215-5784f8168400@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 280 bytes --]

On Thu, Jan 09, 2020 at 07:34:04PM +0100, saravanan sekar wrote:

> Means should I rebase this v6 patch to linux-next and send, or
> of_parse_cb callback changes as separate patch on top of v5?

Send based on -next, no need to resend the other patches which were
already applied.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-01-09 19:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-09 11:25 [PATCH v6 0/4] Add regulator support for mpq7920 Saravanan Sekar
2020-01-09 11:25 ` [PATCH v6 1/4] dt-bindings: Add an entry for Monolithic Power System, MPS Saravanan Sekar
2020-01-13 17:14   ` Rob Herring
2020-01-14 11:53     ` Mark Brown
2020-01-09 11:25 ` [PATCH v6 2/4] dt-bindings: regulator: add document bindings for mpq7920 Saravanan Sekar
2020-01-13 16:56   ` Rob Herring
2020-01-14 12:33     ` Mark Brown
2020-01-09 11:25 ` [PATCH v6 3/4] regulator: mpq7920: add mpq7920 regulator driver Saravanan Sekar
2020-01-09 13:28   ` Mark Brown
2020-01-09 18:34     ` saravanan sekar
2020-01-09 19:16       ` Mark Brown [this message]
2020-01-09 11:25 ` [PATCH v6 4/4] MAINTAINERS: Add entry for mpq7920 PMIC driver Saravanan Sekar

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=20200109191654.GC3702@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=heiko@sntech.de \
    --cc=icenowy@aosc.io \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mchehab+samsung@kernel.org \
    --cc=mripard@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=sam@ravnborg.org \
    --cc=shawnguo@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.