From: Thomas Gleixner <tglx@linutronix.de>
To: speck@linutronix.de
Subject: Re: unreated arch broken by the fixes
Date: Sat, 11 Aug 2018 20:27:26 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1808112021570.1659@nanos.tec.linutronix.de> (raw)
In-Reply-To: <alpine.LFD.2.21.999.1808111041560.25962@i7.lan>
On Sat, 11 Aug 2018, speck for Linus Torvalds wrote:
> On Sat, 11 Aug 2018, Linus Torvalds wrote:
> And more importantly, nobody seems to care about the opposite order. All
> that boot_cpu_state_init() does is about hotplug (which is why Catalin's
> test patch also renamed it to "boot_cpuhp_state_init()" - note the extra
> "hp" in there. I think that renaming might be a good idea (except I'd just
> spell out "hotplug" rather than add "hp" in the middle), but I'm not going
> to do that either.
I was staring at exactly the same place and came to the same conclusion
today in the afternoon, but I had to hurry back into the camp kitchen to
avoid riots of hungry kids.
> End result: keep the sequence as-is, I'll do the re-ordering early in the
> merge window before I pull anything, and mark it for stable.
Ok. I'll ignore it and start to cobble the pull request together.
Thanks,
tglx
prev parent reply other threads:[~2018-08-11 18:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-10 13:27 [MODERATED] unreated arch broken by the fixes Vlastimil Babka
2018-08-10 16:48 ` [MODERATED] " Linus Torvalds
2018-08-10 22:06 ` Linus Torvalds
2018-08-11 7:21 ` Thomas Gleixner
2018-08-11 13:16 ` Thomas Gleixner
2018-08-11 17:34 ` [MODERATED] " Linus Torvalds
2018-08-11 18:02 ` Linus Torvalds
2018-08-11 18:27 ` Thomas Gleixner [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=alpine.DEB.2.21.1808112021570.1659@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=speck@linutronix.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).