From: Shakeel Butt <shakeel.butt@linux.dev>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Christian Brauner <brauner@kernel.org>, Tejun Heo <tj@kernel.org>,
Christian Brauner <christian@brauner.io>,
Meta kernel team <kernel-team@meta.com>,
linux-kselftest@vger.kernel.org, driver-core@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] selftests: cover kernfs dentry revalidation
Date: Fri, 4 Sep 2026 08:34:46 -0700 [thread overview]
Message-ID: <aprkl_CCGJsCPvLO@linux.dev> (raw)
In-Reply-To: <2026090456-unblock-elixir-7d4f@gregkh>
On Fri, Sep 04, 2026 at 04:44:18PM +0200, Greg Kroah-Hartman wrote:
> On Fri, Sep 04, 2026 at 07:33:45AM -0700, Shakeel Butt wrote:
> > On Fri, Sep 04, 2026 at 10:13:11AM +0200, Christian Brauner wrote:
> > > On Tue, Sep 01, 2026 at 06:40:50PM -0700, Shakeel Butt wrote:
[...]
> >
> > I assume the kernfs bug fixes [1] will also go to your vfs branch. I will send a
> > v2 of that series with appropriate tags and will try to improve the commit
> > messages as well. I have a followup improvements for kernfs_rwsem which I will
> > base on vfs branch. Just wanted to give a headsup.
>
> kernfs patches go through the driver-core tree normally, not vfs.
My followup patches depends on patches already in vfs-7.4.kernfs, I will
continue developing on that branch and let you and Christian figure out how
these will go to Linus tree.
Thanks
prev parent reply other threads:[~2026-09-04 15:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 1:40 [PATCH v2] selftests: cover kernfs dentry revalidation Shakeel Butt
2026-09-04 8:07 ` Christian Brauner
2026-09-04 8:13 ` Christian Brauner
2026-09-04 14:33 ` Shakeel Butt
2026-09-04 14:44 ` Greg Kroah-Hartman
2026-09-04 15:34 ` Shakeel Butt [this message]
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=aprkl_CCGJsCPvLO@linux.dev \
--to=shakeel.butt@linux.dev \
--cc=brauner@kernel.org \
--cc=christian@brauner.io \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=tj@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