public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: arnd@arndb.de, ulf.hansson@linaro.org
Cc: Changhuang Liang <changhuang.liang@starfivetech.com>,
	Walker Chen <walker.chen@starfivetech.com>,
	linux-riscv@lists.infradead.org, Rob Herring <robh@kernel.org>,
	Jia Jie Ho <jiajie.ho@starfivetech.com>,
	conor@kernel.org, linux-pm@vger.kernel.org
Subject: Missed soc/genpd PR for 6.6 mw
Date: Mon, 11 Sep 2023 23:11:27 +0100	[thread overview]
Message-ID: <20230911-scouring-squash-3ef2cc8b1ee2@spud> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 822 bytes --]

Hey all,

So I've been informed that I made a hames of things and forgot to send
my soc driver PR for the 6.6 merge window. There's not too much in my
branch
https://git.kernel.org/pub/scm/linux/kernel/git/conor/linux.git/log/?h=riscv-soc-for-next
so I would've kicked the can to 6.7, but the majority of changes there were
made to the starfive pmu driver that has since moved to the new genpd
subsystem.

Sending a PR to Arnd for 6.7 with the pmu bits & based on v6.5-rc1 doesn't
seem to make all that much sense to me, since that stuff is no longer in
drivers/soc, but rebasing on top of v6.6-rc1 would make these genpd changes,
with a different path to Linus.

What's the best way to rectify me screwing this up? Should I split out
the non genpd patch and send a PR for that for the genpd tree for 6.7?

Thanks,
Conor.

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

[-- Attachment #2: Type: text/plain, Size: 161 bytes --]

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

             reply	other threads:[~2023-09-11 22:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-11 22:11 Conor Dooley [this message]
2023-09-12  9:09 ` Missed soc/genpd PR for 6.6 mw Ulf Hansson
2023-09-12 16:05   ` Conor Dooley

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=20230911-scouring-squash-3ef2cc8b1ee2@spud \
    --to=conor@kernel.org \
    --cc=arnd@arndb.de \
    --cc=changhuang.liang@starfivetech.com \
    --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