public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Christian Brauner <brauner@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [GIT pull] timers/core for v6.13-rc1
Date: Wed, 20 Nov 2024 13:12:28 +0100	[thread overview]
Message-ID: <Zz3SLAW-97Zhjfhv@gmail.com> (raw)
In-Reply-To: <20241120-backwaren-faible-99807b4768bb@brauner>


* Christian Brauner <brauner@kernel.org> wrote:

> On Tue, Nov 19, 2024 at 04:33:45PM -0800, Linus Torvalds wrote:
> > On Mon, 18 Nov 2024 at 11:22, Thomas Gleixner <tglx@linutronix.de> wrote:
> > >
> > 
> > >   - Core infrastructure for VFS multigrain timestamping
> > >
> > >     This is required to allow the kernel to use coarse grained time stamps
> > >     by default and switch to fine grained time stamps when inode attributes
> > >     are actively observed via getattr().
> > >
> > >     These changes have been provided to the VFS tree as well, so that the
> > >     VFS specific infrastructure could be built on top.
> > 
> > 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.
> 
> Wait, I'm confused. I definitely pulled that branch the day after Thomas
> gave it to me and in my vfs.mgtime branch I clearly see:
> 
> commit d7c898a73f875bd205df53074c1d542766171da1
> Merge: 8cf0b93919e1 2a15385742c6
> Author:     Christian Brauner <brauner@kernel.org>
> AuthorDate: Mon Oct 7 12:47:19 2024 +0200
> Commit:     Christian Brauner <brauner@kernel.org>
> CommitDate: Thu Oct 10 10:20:57 2024 +0200
> 
>     Merge tag 'timers-core-for-vfs' of ssh://gitolite.kernel.org/pub/scm/linux/kernel/git/tip/tip into vfs.mgtime
> 
>     Timekeeping interfaces for consumption by the VFS tree.
> 
>     Signed-off-by: Christian Brauner <brauner@kernel.org>
> 
> Unless I did something odd during the pull?

The problem was caused by two commits which got rebased in the VFS 
tree:

Commit 1:

  ee3283c608df ("timekeeping: Add interfaces for handling timestamps with a floor value")

  commit ee3283c608dfa21251b0821d7bb198c7ae3189f6
  Author:     Jeff Layton <jlayton@kernel.org>
  AuthorDate: Wed Oct 2 17:27:16 2024 -0400
  Commit:     Christian Brauner <brauner@kernel.org>
  CommitDate: Thu Oct 10 10:20:46 2024 +0200
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Which is a rebase of Thomas's original commit:

  70c8fd00a9bd ("timekeeping: Add interfaces for handling timestamps with a floor value")

  commit 70c8fd00a9bd0509bbf7bccd9baea8bbd5ddc756
  Author:     Jeff Layton <jlayton@kernel.org>
  AuthorDate: Wed Oct 2 17:27:16 2024 -0400
  Commit:     Thomas Gleixner <tglx@linutronix.de>
  CommitDate: Sun Oct 6 20:56:07 2024 +0200

And commit 2:

  2a15385742c6 ("timekeeping: Add percpu counter for tracking floor swap events")

  commit 2a15385742c689a271345dcbb4c28b9c568bc7ce
  Author:     Jeff Layton <jlayton@kernel.org>
  AuthorDate: Wed Oct 2 17:27:17 2024 -0400
  Commit:     Christian Brauner <brauner@kernel.org>
  CommitDate: Thu Oct 10 10:20:46 2024 +0200
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Which is a rebase of Thomas's original commit:

  96f9a366ec8a timekeeping: Add percpu counter for tracking floor swap events

  commit 96f9a366ec8abe027326d7aab84d64370019f0f1 (tag: timers-core-for-vfs)
  Author:     Jeff Layton <jlayton@kernel.org>
  AuthorDate: Wed Oct 2 17:27:17 2024 -0400
  Commit:     Thomas Gleixner <tglx@linutronix.de>
  CommitDate: Sun Oct 6 20:56:07 2024 +0200

Thanks,

	Ingo

  reply	other threads:[~2024-11-20 12:12 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
2024-11-20 10:18     ` Christian Brauner
2024-11-20 12:12       ` Ingo Molnar [this message]
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=Zz3SLAW-97Zhjfhv@gmail.com \
    --to=mingo@kernel.org \
    --cc=brauner@kernel.org \
    --cc=linux-kernel@vger.kernel.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