From: Christian Brauner <brauner@kernel.org>
To: Jan Kara <jack@suse.cz>
Cc: Xing Guo <higuoxing@gmail.com>,
amir73il@gmail.com, jhubbard@nvidia.com,
linux-fsdevel@vger.kernel.org, linux-kselftest@vger.kernel.org,
miklos@szeredi.hu, shuah@kernel.org,
kernel test robot <oliver.sang@intel.com>
Subject: Re: [PATCH] selftests/fs/mount-notify: Fix compilation failure.
Date: Tue, 2 Sep 2025 10:36:09 +0200 [thread overview]
Message-ID: <20250902-abhalten-besehen-ab6959fc4ebb@brauner> (raw)
In-Reply-To: <e4aftint6uauii7p5dvnfd2byllwvzu5hjfxwpa3la3pigmae7@ahw76agoljhh>
On Mon, Sep 01, 2025 at 07:17:07PM +0200, Jan Kara wrote:
> On Wed 13-08-25 15:55:23, Xing Guo wrote:
> > Commit c6d9775c2066 ("selftests/fs/mount-notify: build with tools include
> > dir") introduces the struct __kernel_fsid_t to decouple dependency with
> > headers_install. The commit forgets to define a macro for __kernel_fsid_t
> > and it will cause type re-definition issue.
> >
> > Reported-by: kernel test robot <oliver.sang@intel.com>
> > Closes: https://lore.kernel.org/oe-lkp/202508110628.65069d92-lkp@intel.com
> > Signed-off-by: Xing Guo <higuoxing@gmail.com>
> > Acked-by: Amir Goldstein <amir73il@gmail.com>
>
> Christian, quick search didn't find this patch in your tree. Any reason you
> didn't pick it up?
Weird. Thanks for the reminder, Jan! Picked into vfs.fixes now!
prev parent reply other threads:[~2025-09-02 8:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250813031647.96411-1-higuoxing@gmail.com>
[not found] ` <CAOQ4uxg0OvDW5yJiseEOHBB2sH6Nw1iWo+CvvZ0COTGo=oYmfg@mail.gmail.com>
2025-08-13 6:39 ` [PATCH] selftests/fs/mount-notify: Fix compilation failure Amir Goldstein
2025-08-13 7:55 ` Xing Guo
2025-09-01 17:17 ` Jan Kara
2025-09-02 8:36 ` Christian Brauner [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=20250902-abhalten-besehen-ab6959fc4ebb@brauner \
--to=brauner@kernel.org \
--cc=amir73il@gmail.com \
--cc=higuoxing@gmail.com \
--cc=jack@suse.cz \
--cc=jhubbard@nvidia.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=oliver.sang@intel.com \
--cc=shuah@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