From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Namjae Jeon <linkinjeon@kernel.org>
Cc: Dongliang Cui <dongliang.cui@unisoc.com>,
Zhiguo Niu <zhiguo.niu@unisoc.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the exfat tree
Date: Wed, 18 Sep 2024 08:13:23 +1000 [thread overview]
Message-ID: <20240918081323.760ac7b4@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 497 bytes --]
Hi all,
After merging the exfat tree, today's linux-next build (x86_64
allmodconfig) failed like this:
In file included from fs/exfat/inode.c:18:
fs/exfat/exfat_fs.h:13:10: fatal error: uapi/linux/exfat.h: No such file or directory
13 | #include <uapi/linux/exfat.h>
| ^~~~~~~~~~~~~~~~~~~~
Caused by commit
0636fd914f77 ("exfat: Implement sops->shutdown and ioctl")
I have used the exfat tree from next-20240917 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-09-17 22:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 22:13 Stephen Rothwell [this message]
2024-09-17 22:55 ` linux-next: build failure after merge of the exfat tree Namjae Jeon
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=20240918081323.760ac7b4@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=dongliang.cui@unisoc.com \
--cc=linkinjeon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=zhiguo.niu@unisoc.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