public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Christian Brauner <brauner@kernel.org>,
	linux-kernel@vger.kernel.org, x86@kernel.org,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: [GIT pull] timers/core for v6.13-rc1
Date: Wed, 20 Nov 2024 13:04:22 +0100	[thread overview]
Message-ID: <Zz3QRpWq2alIhA7j@gmail.com> (raw)
In-Reply-To: <20241120094001.GBZz2ucZDr1F08zton@fat_crate.local>


* Borislav Petkov <bp@alien8.de> wrote:

> On Tue, Nov 19, 2024 at 04:33:45PM -0800, Linus Torvalds wrote:
>
> > Bah. Except the vfs tree didn't take it as a shared branch, but 
> > instead cherry-picked the commits and as a result they are 
> > duplicate and caused a (trivial) merge conflict.
> 
> Yeah, we were looking at that last night with tglx and he sent me a 
> resolution (see below) and looking at your tree now, it all looks 
> correct.

So there were two conflicts: one caused by the VFS evil rebase, which 
caused a duplication of two functions within timekeeping.c.

The other conflict was an interaction with the locking tree due to 
overlapping changes, which I resolved in tip:core/merge a couple of 
weeks ago for -next:

  commit 8446247e3ddaf3b173ef96131793bab3f567bd96
  Merge: 2d4cdd3ab714 183ec5f26b2f
  Author: Ingo Molnar <mingo@kernel.org>
  Date:   Wed Nov 6 13:58:08 2024 +0100

    Merge branch 'locking/core' into core/merge, to resolve conflict
    
     Conflicts:
            kernel/time/timekeeping.c
    
    Signed-off-by: Ingo Molnar <mingo@kernel.org>

AFAICT we resolved it in the same way, the only difference is that 
Linus added one more newline for readability.

So we are all good!

Thanks,

	Ingo

  reply	other threads:[~2024-11-20 12:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-18 19:21 [GIT pull] core/debugobjects for v6.13-rc1 Thomas Gleixner
2024-11-18 19:21 ` [GIT pull] irq/core " Thomas Gleixner
2024-11-20  0:49   ` pr-tracker-bot
2024-11-18 19:21 ` [GIT pull] timers/core " Thomas Gleixner
2024-11-20  0:33   ` Linus Torvalds
2024-11-20  9:40     ` Borislav Petkov
2024-11-20 12:04       ` Ingo Molnar [this message]
2024-11-20 10:18     ` Christian Brauner
2024-11-20 12:12       ` Ingo Molnar
2024-11-20 15:48         ` Christian Brauner
2024-11-20 16:10           ` Ingo Molnar
2024-11-20 19:44             ` Christian Brauner
2024-11-22 11:41               ` Christian Brauner
2024-11-20  0:49   ` pr-tracker-bot
2024-11-18 19:22 ` [GIT pull] timers/vdso " Thomas Gleixner
2024-11-20  0:49   ` pr-tracker-bot
2024-11-20  0:49 ` [GIT pull] core/debugobjects " 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=Zz3QRpWq2alIhA7j@gmail.com \
    --to=mingo@kernel.org \
    --cc=bp@alien8.de \
    --cc=brauner@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --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