Li Zetao a24c8b5111 fs/Kconfig: Fix compile error for romfs
There are some compile errors reported by kernel test robot:

arm-linux-gnueabi-ld: fs/romfs/storage.o: in function `romfs_dev_read':
storage.c:(.text+0x64): undefined reference to `__brelse'
arm-linux-gnueabi-ld: storage.c:(.text+0x9c): undefined reference to `__bread_gfp'
arm-linux-gnueabi-ld: fs/romfs/storage.o: in function `romfs_dev_strnlen':
storage.c:(.text+0x128): undefined reference to `__brelse'
arm-linux-gnueabi-ld: storage.c:(.text+0x16c): undefined reference to `__bread_gfp'
arm-linux-gnueabi-ld: fs/romfs/storage.o: in function `romfs_dev_strcmp':
storage.c:(.text+0x22c): undefined reference to `__bread_gfp'
arm-linux-gnueabi-ld: storage.c:(.text+0x27c): undefined reference to `__brelse'
arm-linux-gnueabi-ld: storage.c:(.text+0x2a8): undefined reference to `__bread_gfp'
arm-linux-gnueabi-ld: storage.c:(.text+0x2bc): undefined reference to `__brelse'
arm-linux-gnueabi-ld: storage.c:(.text+0x2d4): undefined reference to `__brelse'
arm-linux-gnueabi-ld: storage.c:(.text+0x2f4): undefined reference to `__brelse'
arm-linux-gnueabi-ld: storage.c:(.text+0x304): undefined reference to `__brelse'

The reason for the problem is that the commit
"925c86a19bac" ("fs: add CONFIG_BUFFER_HEAD") has added a new config
"CONFIG_BUFFER_HEAD" that controls building the buffer_head code, and
romfs needs to use the buffer_head API, but no corresponding config has
beed added. Select the config "CONFIG_BUFFER_HEAD" in romfs Kconfig to
resolve the problem.

Fixes: 925c86a19bac ("fs: add CONFIG_BUFFER_HEAD")
Reported-by: kernel test robot <lkp@intel.com>
Closes: https://lore.kernel.org/oe-kbuild-all/202308031810.pQzGmR1v-lkp@intel.com/
Reviewed-by: Luis Chamberlain <mcgrof@kernel.org>
Tested-by: Li Zetao <lizetao1@huawei.com>
Signed-off-by: Li Zetao <lizetao1@huawei.com>
[axboe: fold in Christoph's incremental]
Signed-off-by: Jens Axboe <axboe@kernel.dk>
2023-08-04 11:04:05 -06:00
..
2023-05-24 08:42:16 -06:00
2023-08-02 09:13:09 -06:00
2023-08-02 09:13:09 -06:00
2023-08-02 09:13:09 -06:00
2023-08-02 09:13:09 -06:00
2023-06-26 10:14:36 -07:00
2023-05-24 08:42:16 -06:00
2023-06-29 13:27:50 -07:00
2023-08-02 09:13:09 -06:00
2023-08-02 09:13:09 -06:00
2023-08-02 09:13:09 -06:00
2023-08-02 09:13:09 -06:00
2023-08-02 09:13:09 -06:00
2023-08-02 09:13:09 -06:00
2023-08-02 09:13:09 -06:00
2023-07-01 08:48:02 -07:00
2023-08-02 09:13:09 -06:00
2023-08-02 09:13:09 -06:00
2023-08-02 09:13:09 -06:00
2023-06-27 17:10:27 -07:00
2023-08-02 09:13:09 -06:00
2023-08-02 09:13:09 -06:00
2023-06-26 11:52:12 -07:00
2023-08-02 09:13:09 -06:00
2023-07-03 12:56:23 -07:00
2023-07-01 14:38:25 -07:00
2023-08-02 09:13:09 -06:00
2023-07-01 14:38:25 -07:00
2023-06-30 21:48:44 -07:00
2023-08-02 09:13:09 -06:00
2023-08-02 09:13:09 -06:00
2023-08-02 09:13:09 -06:00
2023-08-02 09:13:09 -06:00
2023-08-02 09:13:09 -06:00
2023-07-06 10:06:04 -07:00
2023-06-27 21:21:32 -07:00
2023-08-02 09:13:09 -06:00
2023-08-02 09:13:09 -06:00
2023-06-05 16:50:30 +02:00
2023-08-02 09:13:09 -06:00
2023-06-15 13:37:53 +02:00
2023-08-02 09:13:09 -06:00
2023-08-02 09:13:09 -06:00
2023-08-02 09:13:09 -06:00
2023-06-27 21:24:18 -07:00
2023-07-09 09:50:42 -07:00
2023-03-30 08:51:48 +02:00
2023-06-28 20:35:21 -07:00
2023-08-02 09:13:09 -06:00
2023-06-26 09:50:21 -07:00
2023-05-17 09:16:59 +02:00
2023-06-26 09:50:21 -07:00
\n
2023-06-29 13:31:44 -07:00
2023-02-20 11:53:11 -08:00
2023-08-02 09:13:09 -06:00
2023-08-02 09:13:09 -06:00
2023-08-02 09:13:09 -06:00
2023-01-19 09:24:30 +01:00
2023-07-04 10:20:29 +02:00
2023-06-26 10:27:04 -07:00
\n
2023-06-29 13:31:44 -07:00
2023-05-19 04:30:22 +02:00
2023-05-19 04:30:22 +02:00
2023-03-06 09:59:20 +01:00
2023-06-28 16:43:10 -07:00
2023-02-20 11:53:11 -08:00
2023-08-02 09:13:09 -06:00
2023-02-20 11:53:11 -08:00