public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

From: Guan-Chun Wu <409411716@gms•tku.edu.tw>
To: Mark Brown <broonie@kernel•org>
Cc: Theodore Ts'o <tytso@mit•edu>,
	Chen Hao Yu <edward062254@gmail•com>,
	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 ext4 tree
Date: Mon, 1 Jun 2026 23:17:47 +0800	[thread overview]
Message-ID: <ah2imxo7xs2+kUEC@wu-Pro-E500-G6-WS720T> (raw)
In-Reply-To: <704d573d-267f-41b7-8204-5135848ec9c1@sirena.org.uk>

On Mon, Jun 01, 2026 at 01:43:44PM +0100, Mark Brown wrote:
> On Fri, May 29, 2026 at 12:59:36PM +0100, Mark Brown wrote:
> > Hi all,
> > 
> > After merging the ext4 tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> > 
> > ERROR: modpost: "ext4fs_dirhash" [fs/ext4/ext4-test.ko] undefined!
> > 
> > Caused by commit
> > 
> >    a4841d91a7f57 (ext4: add Kunit coverage for directory hash computation)
> > 
> > I have used the tree from next-20260528 instead.
> 
> This issue is still present today.

Hi Mark,

Thanks for reporting this.

I have sent an updated version of the patch series that should address this
issue:

Link: https://lore.kernel.org/lkml/20260531080019.3794809-1-409411716@gms.tku.edu.tw/

Please let me know if anything else is needed.

Thanks,
Guan-Chun

next prev parent reply	other threads:[~2026-06-01 15:17 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-29 11:59 linux-next: build failure after merge of the ext4 tree Mark Brown
2026-06-01 12:43 ` Mark Brown
2026-06-01 15:17   ` Guan-Chun Wu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-07-14 22:22 Stephen Rothwell
2025-07-15  3:31 ` Zhang Yi
2025-02-13 22:58 Stephen Rothwell
2018-10-08 23:51 Stephen Rothwell
2018-10-09  5:23 ` Theodore Y. Ts'o
2016-02-07 23:50 Stephen Rothwell
2016-01-03 23:34 Stephen Rothwell
2016-01-04 13:49 ` Theodore Ts'o
2015-07-23  0:56 Stephen Rothwell
2015-07-23 16:49 ` Theodore Ts'o
2015-07-23 17:23   ` Theodore Ts'o
2015-07-23 17:41     ` Tejun Heo
2015-05-07  1:14 Stephen Rothwell
2013-07-29  1:08 Stephen Rothwell
2013-07-31  1:27 ` Stephen Rothwell
2013-08-07  5:16 ` Sedat Dilek
2013-08-07  5:38   ` Stephen Rothwell
2013-08-07  5:43     ` Sedat Dilek
2013-08-07  5:59       ` Stephen Rothwell
2013-08-07 15:28     ` Kevin Hilman
2013-08-08  0:22       ` Stephen Rothwell
2013-08-08  0:36         ` Stephen Rothwell
2013-08-08 19:16           ` Yann E. MORIN
2013-08-08 21:54             ` Yann E. MORIN
2013-08-08 23:58               ` Stephen Rothwell
2013-08-09 11:42               ` Sam Ravnborg
2013-08-11 21:39                 ` Yann E. MORIN
2013-08-16 13:10                   ` Michal Marek
2013-08-16 17:14                     ` Sam Ravnborg
2013-08-16 18:02                       ` Yann E. MORIN
2013-04-03 23:43 Stephen Rothwell
2013-04-04 13:18 ` Lukáš Czerner
2013-04-04 13:20   ` Theodore Ts'o
2013-04-04 13:27     ` Lukáš Czerner
2012-07-10  1:23 Stephen Rothwell
2012-07-10  1:48 ` Aditya Kali
2012-01-03  0:35 Stephen Rothwell
2012-01-05 21:06 ` Stephen Rothwell

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=ah2imxo7xs2+kUEC@wu-Pro-E500-G6-WS720T \
    --to=409411716@gms$(echo .)tku.edu.tw \
    --cc=broonie@kernel$(echo .)org \
    --cc=edward062254@gmail$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=tytso@mit$(echo .)edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox