public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor.dooley@microchip.com>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Conor Dooley <conor@kernel.org>, <arnd@arndb.de>,
	<changhuang.liang@starfivetech.com>, <jiajie.ho@starfivetech.com>,
	<linux-pm@vger.kernel.org>, <linux-riscv@lists.infradead.org>,
	<robh@kernel.org>, <walker.chen@starfivetech.com>
Subject: Re: [GIT PULL 0/5] Missed starfive pmdomain changes for v6.6, now for v6.7
Date: Thu, 14 Sep 2023 07:46:27 +0100	[thread overview]
Message-ID: <20230914-appliance-vastness-989ded32323a@wendy> (raw)
In-Reply-To: <CAPDyKFoENVp7+VjKkPpJWDecowxYD=QM6TSa6HjyzOZ=z7r81w@mail.gmail.com>

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

Yo,

I tried to reply a few hours ago from k9, but it appears to not have
landed on lore, so here goes attempt #2. Apologies if you got a mail
twice.

On Thu, Sep 14, 2023 at 12:30:20AM +0200, Ulf Hansson wrote:
> On Wed, 13 Sept 2023 at 15:56, Conor Dooley <conor@kernel.org> wrote:
> >
> > From: Conor Dooley <conor.dooley@microchip.com>
> >
> > Hey Uffe,
> >
> > Here's those missed changes in patch form. I figured it might be a bit
> > easier this way given the name of the subsystem is in flux, doubly so if
> > you'd like to put the header change of Rob's on fixes.
> 
> Not sure we really need to queue up patch 1 for fixes - or is it
> fixing a real problem for us?

It was just in case you felt that taking that header cleanup as a fix
was worthwhile. I think I saw some people doing that last cycle & I
think Rob was trying to clean that up for v6.6 which I obviously haven't
helped him with.

> The series applied for next, thanks!

Great, thanks.

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

  reply	other threads:[~2023-09-14  6:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-13 13:54 [GIT PULL 0/5] Missed starfive pmdomain changes for v6.6, now for v6.7 Conor Dooley
2023-09-13 13:54 ` [GIT PULL 1/5] pmdomain: starfive: Explicitly include correct DT includes Conor Dooley
2023-09-13 13:54 ` [GIT PULL 2/5] dt-bindings: power: Add power-domain header for JH7110 Conor Dooley
2023-09-26 10:55   ` Geert Uytterhoeven
2023-09-26 11:20     ` Conor Dooley
2023-09-27  1:31       ` Changhuang Liang
2023-09-27  1:24     ` Changhuang Liang
2023-09-27  7:12       ` Geert Uytterhoeven
2023-09-27 13:26     ` Changhuang Liang
2023-09-13 13:54 ` [GIT PULL 3/5] pmdomain: starfive: Replace SOC_STARFIVE with ARCH_STARFIVE Conor Dooley
2023-09-13 13:54 ` [GIT PULL 4/5] pmdomain: starfive: Extract JH7110 pmu private operations Conor Dooley
2023-09-13 13:54 ` [GIT PULL 5/5] pmdomain: starfive: Add JH7110 AON PMU support Conor Dooley
2023-09-13 22:30 ` [GIT PULL 0/5] Missed starfive pmdomain changes for v6.6, now for v6.7 Ulf Hansson
2023-09-14  6:46   ` Conor Dooley [this message]
2023-09-14 13:57   ` Rob Herring
2023-09-14 14:09     ` Ulf Hansson

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=20230914-appliance-vastness-989ded32323a@wendy \
    --to=conor.dooley@microchip.com \
    --cc=arnd@arndb.de \
    --cc=changhuang.liang@starfivetech.com \
    --cc=conor@kernel.org \
    --cc=jiajie.ho@starfivetech.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=robh@kernel.org \
    --cc=ulf.hansson@linaro.org \
    --cc=walker.chen@starfivetech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox