Linux-GPIO Archive on lore.kernel.org
 help / color / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Lars Povlsen <lars.povlsen@microchip.com>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
	SoC Team <soc@kernel.org>, Stephen Boyd <sboyd@kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Steen Hegelund <Steen.Hegelund@microchip.com>,
	Microchip Linux Driver Support <UNGLinuxDriver@microchip.com>,
	Olof Johansson <olof@lixom.net>,
	Michael Turquette <mturquette@baylibre.com>,
	DTML <devicetree@vger.kernel.org>,
	linux-clk <linux-clk@vger.kernel.org>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 00/10] Adding support for Microchip Sparx5 SoC
Date: Mon, 27 Jul 2020 13:07:14 +0200
Message-ID: <CAK8P3a0CMqqFWM+QXC0wXxrfKBN0U5cyx_naBx+hS3V3SG2KOQ@mail.gmail.com> (raw)
In-Reply-To: <87v9i9fdy7.fsf@soft-dev15.microsemi.net>

On Mon, Jul 27, 2020 at 12:30 PM Lars Povlsen
<lars.povlsen@microchip.com> wrote:
> Alexandre Belloni writes:
> > As Arnd stated, he already applied the patches so you have to send an
> > incremental patch to fix the clock driver.
> >
>
> I actually wrote Arnd about this specifically, and he replied that a
> patch against either next or mainline was fine - so that's why I
> refreshed the lot (Including Reviewed-by: headers).

I think I misunderstood your question. To clarify: Alexandre is right,
you should not resend patches that have already been merged but
instead send the incremental patches if you need further changes.

I thought your question was about the case where your patch
series has conflicts against another unrelated set of changes
that may have been merged already.

> But I will send an incremental patch just in case, no problem.

Thanks,

      Arnd

      reply index

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-27  8:42 Lars Povlsen
2020-07-27  8:42 ` [PATCH v4 01/10] dt-bindings: arm: sparx5: Add documentation " Lars Povlsen
2020-07-27  8:42 ` [PATCH v4 02/10] arm64: sparx5: Add support for Microchip 2xA53 SoC Lars Povlsen
2020-07-27  8:42 ` [PATCH v4 03/10] arm64: dts: sparx5: Add basic cpu support Lars Povlsen
2020-07-27  8:42 ` [PATCH v4 04/10] arm64: dts: sparx5: Add pinctrl support Lars Povlsen
2020-07-27  8:42 ` [PATCH v4 05/10] pinctrl: ocelot: Add Sparx5 SoC support Lars Povlsen
2020-07-27  8:42 ` [PATCH v4 06/10] dt-bindings: clock: sparx5: Add Sparx5 SoC DPLL clock Lars Povlsen
2020-07-27  8:42 ` [PATCH v4 07/10] dt-bindings: clock: sparx5: Add bindings include file Lars Povlsen
2020-07-27  8:42 ` [PATCH v4 08/10] clk: sparx5: Add Sparx5 SoC DPLL clock driver Lars Povlsen
2020-07-27  8:42 ` [PATCH v4 09/10] arm64: dts: sparx5: Add Sparx5 SoC DPLL clock Lars Povlsen
2020-07-27  8:42 ` [PATCH v4 10/10] arm64: dts: sparx5: Add i2c devices, i2c muxes Lars Povlsen
2020-07-27  9:50 ` [PATCH v4 00/10] Adding support for Microchip Sparx5 SoC Alexandre Belloni
2020-07-27 10:29   ` Lars Povlsen
2020-07-27 11:07     ` Arnd Bergmann [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=CAK8P3a0CMqqFWM+QXC0wXxrfKBN0U5cyx_naBx+hS3V3SG2KOQ@mail.gmail.com \
    --to=arnd@arndb.de \
    --cc=Steen.Hegelund@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=devicetree@vger.kernel.org \
    --cc=lars.povlsen@microchip.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=olof@lixom.net \
    --cc=sboyd@kernel.org \
    --cc=soc@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

Linux-GPIO Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-gpio/0 linux-gpio/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-gpio linux-gpio/ https://lore.kernel.org/linux-gpio \
		linux-gpio@vger.kernel.org
	public-inbox-index linux-gpio

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-gpio


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git