linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Stephen Boyd <sboyd@kernel.org>
Cc: Lars Povlsen <lars.povlsen@microchip.com>,
	SoC Team <soc@kernel.org>,
	Steen Hegelund <Steen.Hegelund@microchip.com>,
	Microchip Linux Driver Support <UNGLinuxDriver@microchip.com>,
	linux-clk <linux-clk@vger.kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>
Subject: Re: [PATCH linux-next] clk: sparx5: Review changes
Date: Tue, 28 Jul 2020 11:23:41 +0200	[thread overview]
Message-ID: <CAK8P3a2io+cn0phoGDfpNvp-2gOXDaKyi8Me3Pz0k+VjbmwGFw@mail.gmail.com> (raw)
In-Reply-To: <159588781925.1360974.3928941757935200801@swboyd.mtv.corp.google.com>

On Tue, Jul 28, 2020 at 12:10 AM Stephen Boyd <sboyd@kernel.org> wrote:
> Quoting Arnd Bergmann (2020-07-27 13:11:49)
> > I rebased the 'arm/newsoc' branch the other day to fix another mistake,
> > so if you prefer, I can rebase it again and drop the clk driver or
> > all the sparx5 patches.
> >
>
> Yes, please just drop the clk driver and I can pick it up for the next
> merge window from the list and all the fixes can be rolled into one
> patch.

Done.

     Arnd

      parent reply	other threads:[~2020-07-28  9:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-27 11:22 [PATCH linux-next] clk: sparx5: Review changes Lars Povlsen
2020-07-27 12:02 ` Arnd Bergmann
     [not found]   ` <159587873833.1360974.11729154337431621644@swboyd.mtv.corp.google.com>
2020-07-27 20:11     ` Arnd Bergmann
     [not found]       ` <159588781925.1360974.3928941757935200801@swboyd.mtv.corp.google.com>
2020-07-28  7:53         ` Lars Povlsen
2020-07-28  9:23         ` 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=CAK8P3a2io+cn0phoGDfpNvp-2gOXDaKyi8Me3Pz0k+VjbmwGFw@mail.gmail.com \
    --to=arnd@arndb.de \
    --cc=Steen.Hegelund@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=lars.povlsen@microchip.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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
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).