From: Tejun Heo <tj@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Max Kellermann <max.kellermann@ionos.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs/kernfs: implement STATX_BTIME
Date: Wed, 21 May 2025 06:18:51 -1000 [thread overview]
Message-ID: <aC386_UJaBxf5WTE@slm.duckdns.org> (raw)
In-Reply-To: <2025052100-depravity-founder-6332@gregkh>
On Wed, May 21, 2025 at 01:24:36PM +0200, Greg KH wrote:
...
> > (It's okay if you don't like the patch and it doesn't get merged - as
> > always, I can happily keep it in our private kernel fork. I'm only
> > offering my work to everybody, because I'm a strong believer in open
> > source.)
>
> I feel like the creation time here is odd, but if others really
> need/want it we could take it. I would like to see others review it
> though.
Isn't this trivially trackable from userspace with udev?
Thanks.
--
tejun
next prev parent reply other threads:[~2025-05-21 16:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 16:40 [PATCH] fs/kernfs: implement STATX_BTIME Max Kellermann
2025-05-06 17:43 ` Greg KH
2025-05-06 18:30 ` Max Kellermann
2025-05-21 11:24 ` Greg KH
2025-05-21 16:18 ` Tejun Heo [this message]
2025-05-21 20:19 ` Max Kellermann
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=aC386_UJaBxf5WTE@slm.duckdns.org \
--to=tj@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=max.kellermann@ionos.com \
/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