linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Matthew Wilcox <willy@infradead.org>
Cc: kernel test robot <lkp@intel.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	linux-arm-msm@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-rtc@vger.kernel.org, linux-serial@vger.kernel.org,
	Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>
Subject: Re: [linux-next:master] BUILD REGRESSION fb4327106e5250ee360d0d8b056c1eef7eeb9a98
Date: Fri, 4 Aug 2023 12:22:18 +0200	[thread overview]
Message-ID: <20230804102218.GD23274@lst.de> (raw)
In-Reply-To: <ZMwH1WuEb1JEtZ4o@casper.infradead.org>

On Thu, Aug 03, 2023 at 09:02:29PM +0100, Matthew Wilcox wrote:
> I think something like this would fix it.  Jens?  Christoph?
> 
> +++ b/fs/romfs/Kconfig
> @@ -2,6 +2,7 @@
>  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
> 
> romfs has a few options and I spent no time looking at this closely;
> maybe not every version of romfs needs buffer heads.

It only needs buffer_heads for the block based path.  I'll send a patch
for it.


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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-03 17:34 kernel test robot
2023-08-03 20:02 ` Matthew Wilcox
2023-08-04  2:02   ` Jens Axboe
2023-08-04 10:22   ` Christoph Hellwig [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=20230804102218.GD23274@lst.de \
    --to=hch@lst.de \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@kernel.dk \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-rtc@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=willy@infradead.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