All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [GIT pull] x86/core for v6.5-rc1
Date: Tue, 27 Jun 2023 00:18:28 +0200	[thread overview]
Message-ID: <87zg4l50ln.ffs@tglx> (raw)
In-Reply-To: <CAHk-=wgoVt9izQi2iA3F8PZbnmT+r4CcqaHp+FhEozSj2D=UFg@mail.gmail.com>

Linus!

On Mon, Jun 26 2023 at 15:00, Linus Torvalds wrote:
> On Mon, 26 Jun 2023 at 05:14, Thomas Gleixner <tglx@linutronix.de> wrote:
>>
>> This conflicts with smp/core and x86/boot. The recommended ordering of
>> merging these three branches is smp/core, x86/boot, x86/core.
>>
>> The x86/boot and final x86/core merge have both subtle conflicts. I've
>> pushed out the following tags:
>>
>>    git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git merge_smp_core_x86_boot_for_6_5
>>    git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git merge_smp_core_x86_boot_x86_core_for_6_5
>>
>> for your conveniance to check against.
>
> Bah. I read this after I had already done the merges in a different
> order, and my result is a bit different from your merges.

I see you started with x86/boot, which has a similar note. I clearly
missed to add one to smp/core :)

> All my differences seem to be benign, though. The main one seems to be
> that I kept a preempt_disable/preempt_enable pair in
> wakeup_secondary_cpu_via_init(), the others seem to be just comments
> and declaration ordering changes.

That's fine. I do the comment fixup and the preempt_*able() removal in a
follow up.

> Still, you might want to double-check the end result.

Other than the cosmetic issues you noticed yourself, it's all good.

Thanks,

        tglx

  reply	other threads:[~2023-06-26 22:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-26 12:13 [GIT pull] core/debugobjects for v6.5-rc1 Thomas Gleixner
2023-06-26 12:13 ` [GIT pull] irq/core " Thomas Gleixner
2023-06-26 22:06   ` pr-tracker-bot
2023-06-26 12:13 ` [GIT pull] smp/core " Thomas Gleixner
2023-06-26 22:06   ` pr-tracker-bot
2023-06-26 12:13 ` [GIT pull] timers/core " Thomas Gleixner
2023-06-26 22:06   ` pr-tracker-bot
2023-06-26 12:13 ` [GIT pull] x86/boot " Thomas Gleixner
2023-06-26 22:06   ` pr-tracker-bot
2023-06-26 12:13 ` [GIT pull] x86/core " Thomas Gleixner
2023-06-26 22:00   ` Linus Torvalds
2023-06-26 22:18     ` Thomas Gleixner [this message]
2023-06-26 22:06   ` pr-tracker-bot
2023-06-26 22:06 ` [GIT pull] core/debugobjects " pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2023-07-09 11:57 [GIT pull] x86/core " Thomas Gleixner
2023-07-09 17:46 ` pr-tracker-bot

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=87zg4l50ln.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.