mirror of
git://git.yoctoproject.org/linux-yocto.git
synced 2025-08-22 00:42:01 +02:00

Add a new config option that controls building the buffer_head code, and select it from all file systems and stacking drivers that need it. For the block device nodes and alternative iomap based buffered I/O path is provided when buffer_head support is not enabled, and iomap needs a a small tweak to define the IOMAP_F_BUFFER_HEAD flag to 0 to not call into the buffer_head code when it doesn't exist. Otherwise this is just Kconfig and ifdef changes. Signed-off-by: Christoph Hellwig <hch@lst.de> Reviewed-by: Luis Chamberlain <mcgrof@kernel.org> Reviewed-by: Johannes Thumshirn <johannes.thumshirn@wdc.com> Link: https://lore.kernel.org/r/20230801172201.1923299-7-hch@lst.de Signed-off-by: Jens Axboe <axboe@kernel.dk>
889 B
889 B
SPDX-License-Identifier: GPL-2.0-only
config QNX6FS_FS tristate "QNX6 file system support (read only)" depends on BLOCK && CRC32 select BUFFER_HEAD help This is the file system used by the real-time operating systems QNX 6 (also called QNX RTP). Further information is available at http://www.qnx.com/. Say Y if you intend to mount QNX hard disks or floppies formatted with a mkqnx6fs. However, keep in mind that this currently is a readonly driver!
To compile this file system support as a module, choose M here: the
module will be called qnx6.
If you don't know whether you need it, then you don't need it:
answer N.
config QNX6FS_DEBUG bool "QNX6 debugging information" depends on QNX6FS_FS help Turns on extended debugging output.
If you are not a developer working on the QNX6FS, you probably don't
want this:
answer N.