public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Gao Xiang <xiang@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the erofs-fixes tree
Date: Fri, 13 Dec 2024 08:40:56 +0800	[thread overview]
Message-ID: <9035af43-cecc-4082-bdc1-4698a1dce502@linux.alibaba.com> (raw)
In-Reply-To: <20241213101602.745dc685@canb.auug.org.au>



On 2024/12/13 07:16, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the erofs-fixes tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> fs/erofs/fscache.c: In function 'erofs_fscache_bio_alloc':
> fs/erofs/fscache.c:201:30: error: 'struct erofs_map_dev' has no member named 'm_fscache'
>    201 |         io->io.private = mdev->m_fscache->cookie;
>        |                              ^~
> fs/erofs/fscache.c: In function 'erofs_fscache_data_read_slice':
> fs/erofs/fscache.c:319:47: error: 'struct erofs_map_dev' has no member named 'm_fscache'
>    319 |         ret = erofs_fscache_read_io_async(mdev.m_fscache->cookie,
>        |                                               ^
> 
> Caused by commit
> 
>    34cff83201d5 ("erofs: reference `struct erofs_device_info` for erofs_map_dev")
> 
> I have used the erofs-fixes tree from next-20241212 for today.

Thanks, fixed and pushed.

Thanks,
Gao Xiang

> 


      reply	other threads:[~2024-12-13  0:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-12 23:16 linux-next: build failure after merge of the erofs-fixes tree Stephen Rothwell
2024-12-13  0:40 ` Gao Xiang [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=9035af43-cecc-4082-bdc1-4698a1dce502@linux.alibaba.com \
    --to=hsiangkao@linux.alibaba.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=xiang@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