linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Ingo Molnar <mingo@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	the arch/x86 maintainers <x86@kernel.org>
Subject: Re: [GIT pull] core/urgent for v5.14-rc3
Date: Sun, 25 Jul 2021 21:49:16 +0200	[thread overview]
Message-ID: <878s1unphf.ffs@nanos.tec.linutronix.de> (raw)
In-Reply-To: <CAHk-=wj5BnPvhmFkXuTJKHawi9kRQsFQDO44GQ4XzqJbwupSWw@mail.gmail.com>

On Sun, Jul 25 2021 at 11:06, Linus Torvalds wrote:
> On Sun, Jul 25, 2021 at 2:23 AM Thomas Gleixner <tglx@linutronix.de> wrote:
> So that function definition _should_ have been
>
>     static __always_inline void idle_init(unsigned int cpu)
>
> instead.
>
> Oh well. I'll fix it up as a separate patch. I wish I had done the
> clang build before pushing it out - and I wish the -tip tree started
> tested clang as well at least in _some_ configuration.

Bah, obvious and I overlooked it when staring at the diff. Duly noted
that clang will be part of the procedure soonish.

Thanks,

        tglx

      reply	other threads:[~2021-07-25 19:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-25  9:22 [GIT pull] core/urgent for v5.14-rc3 Thomas Gleixner
2021-07-25  9:22 ` [GIT pull] efi/urgent " Thomas Gleixner
2021-07-25 17:49   ` pr-tracker-bot
2021-07-25  9:22 ` [GIT pull] locking/urgent " Thomas Gleixner
2021-07-25 17:49   ` pr-tracker-bot
2021-07-25  9:22 ` [GIT pull] timers/urgent " Thomas Gleixner
2021-07-25 17:49   ` pr-tracker-bot
2021-07-25 17:49 ` [GIT pull] core/urgent " pr-tracker-bot
2021-07-25 18:06 ` Linus Torvalds
2021-07-25 19:49   ` 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=878s1unphf.ffs@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@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).