mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Li Zetao <lizetao1@huawei.com>
To: Christoph Hellwig <hch@infradead.org>, <axboe@kernel.dk>
Cc: <linux-block@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] romfs: only select BUFFER_HEAD for the block based path
Date: Fri, 4 Aug 2023 18:57:48 +0800	[thread overview]
Message-ID: <a59cb5df-ad95-61d8-b93c-ca993651f82f@huawei.com> (raw)
In-Reply-To: <20230804102648.78683-1-hch@infradead.org>

Hi Christoph,

On 2023/8/4 18:26, Christoph Hellwig wrote:
> selecting BUFFER_HEAD unconditionally does not work as romfs can also
> be built with only the MTD backend and thus without CONFIG_BLOCK.
> 
> Fixes: 0f842210d97a ("fs/Kconfig: Fix compile error for romfs")
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
>   fs/romfs/Kconfig | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/fs/romfs/Kconfig b/fs/romfs/Kconfig
> index 3f6b550eee6192..f24a96a331af1b 100644
> --- a/fs/romfs/Kconfig
> +++ b/fs/romfs/Kconfig
> @@ -2,7 +2,6 @@
>   config ROMFS_FS
>   	tristate "ROM file system support"
>   	depends on BLOCK || MTD
> -	select BUFFER_HEAD
>   	help
>   	  This is a very small read-only file system mainly intended for
>   	  initial ram disks of installation disks, but it could be used for
> @@ -58,6 +57,7 @@ endchoice
>   config ROMFS_ON_BLOCK
>   	bool
>   	default y if ROMFS_BACKED_BY_BLOCK || ROMFS_BACKED_BY_BOTH
> +	select BUFFER_HEAD
>   
>   config ROMFS_ON_MTD
>   	bool

I have tested the patch on my environment and it resolves the two 
compile errors reported by kernel test robot. The links are as follows:

Link1: 
https://lore.kernel.org/oe-kbuild-all/202308031810.pQzGmR1v-lkp@intel.com/
Link2: 
https://lore.kernel.org/oe-kbuild-all/202308041329.6SK97Asr-lkp@intel.com/

Tested-by: Li Zetao <lizetao1@huawei.com>

Thanks,
Li Zetao

  parent reply	other threads:[~2023-08-04 10:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-04 10:26 Christoph Hellwig
2023-08-04 10:38 ` Christoph Hellwig
2023-08-04 10:57 ` Li Zetao [this message]
2023-08-04 17:31 ` Jens Axboe

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=a59cb5df-ad95-61d8-b93c-ca993651f82f@huawei.com \
    --to=lizetao1@huawei.com \
    --cc=axboe@kernel.dk \
    --cc=hch@infradead.org \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®