From: Christian Brauner <brauner@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: 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 11:18:50 +0100 [thread overview]
Message-ID: <20241120-backwaren-faible-99807b4768bb@brauner> (raw)
In-Reply-To: <CAHk-=wiX7=bqOEO06+BsO_25dHoa=KBWcNzLg=-rAKJ=dqKxYg@mail.gmail.com>
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?
next prev parent reply other threads:[~2024-11-20 10:18 UTC|newest]
Thread overview: 11+ 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 10:18 ` Christian Brauner [this message]
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=20241120-backwaren-faible-99807b4768bb@brauner \
--to=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