From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 3/3] arm: kernel: implement cpuidle_ops with psci backend
Date: Mon, 27 Jul 2015 10:45:07 +0100 [thread overview]
Message-ID: <20150727094507.GD7557@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20150727091602.GA10308@red-moon>
On Mon, Jul 27, 2015 at 10:16:02AM +0100, Lorenzo Pieralisi wrote:
> Yes, I would only ask you, if the plan above (which can be implemented
> in two steps) makes sense to you please consider accepting Mark's change
> to consolidate PSCI code into drivers/firmware/psci, it is a stepping stone
> without which the changes above can't happen, I will take charge of completing
> the move of CPUidle code and create the required shim layer into
> drivers to make this happen.
Why can't Jisheng Zhang base his patches on top of Mark's changes and
place the new file directly under drivers/ ?
Why do it as a two-step process with it first appearing in arch/arm,
and then having to generate another patch at a later date to move it
elsewhere. That just creates more noise, and we should be avoiding
generating noise in arch/arm.
This is what Linus has said in his -rc4 release notes yesterday:
Other than that issue, it's mostly drivers and networking. USB, gpu,
mmc, network drivers, sound. With some ARM noise (but even that is
mostly driver-related: dts updates due to MMC fixes). And a few small
filesystem fixes.
and we can infer from the phrase "ARM noise" that Linus' opinion of
arch/arm is still fairly low, and still doesn't regard the "churn" in
arch/arm as being useful.
--
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2015-07-27 9:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 8:31 [PATCH v3 0/3] arm: kernel: implement cpuidle_ops with psci backend Jisheng Zhang
2015-07-09 8:31 ` [PATCH v3 1/3] firmware: psci: move cpu_suspend handling to generic code Jisheng Zhang
2015-07-09 8:31 ` [PATCH v3 2/3] ARM: cpuidle: refine cpuidle_ops member's parameters Jisheng Zhang
2015-07-09 8:43 ` Jisheng Zhang
2015-07-09 9:28 ` Lorenzo Pieralisi
2015-07-10 15:07 ` Lina Iyer
2015-07-10 17:37 ` Lina Iyer
2015-07-09 8:31 ` [PATCH v3 3/3] arm: kernel: implement cpuidle_ops with psci backend Jisheng Zhang
2015-07-14 10:34 ` Russell King - ARM Linux
2015-07-14 11:03 ` Lorenzo Pieralisi
2015-07-14 12:29 ` Russell King - ARM Linux
2015-07-14 14:55 ` Lorenzo Pieralisi
2015-07-14 20:41 ` Russell King - ARM Linux
2015-07-15 13:46 ` Lorenzo Pieralisi
2015-07-15 14:45 ` Russell King - ARM Linux
2015-07-15 15:40 ` Lorenzo Pieralisi
2015-07-26 21:45 ` Russell King - ARM Linux
2015-07-27 9:16 ` Lorenzo Pieralisi
2015-07-27 9:45 ` Russell King - ARM Linux [this message]
2015-07-27 10:01 ` Lorenzo Pieralisi
2015-07-27 10:09 ` Russell King - ARM Linux
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=20150727094507.GD7557@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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).