linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Tejun Heo <tj@kernel.org>
Subject: Re: linux-next: build failure after merge of the ext4 tree
Date: Thu, 23 Jul 2015 12:49:53 -0400	[thread overview]
Message-ID: <20150723164953.GA15778@thunk.org> (raw)
In-Reply-To: <20150723105623.2f8c9548@canb.auug.org.au>

On Thu, Jul 23, 2015 at 10:56:23AM +1000, Stephen Rothwell wrote:
> Hi Theodore,
> 
> After merging the ext4 tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> ERROR: "wbc_account_io" [fs/ext4/ext4.ko] undefined!
> ERROR: "bio_associate_blkcg" [fs/ext4/ext4.ko] undefined!
> 
> Caused by commit
> 
>   001e4a8775f6 ("ext4: implement cgroup writeback support")
> 
> I have used the ext4 tree from next-20150722 for today.

Ah, I see, we're missing the include files which define the inline
dummy functions.  I'll fix this in my tree, thanks.

      		       	   	      	    - Ted

  reply	other threads:[~2015-07-23 16:50 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-23  0:56 linux-next: build failure after merge of the ext4 tree Stephen Rothwell
2015-07-23 16:49 ` Theodore Ts'o [this message]
2015-07-23 17:23   ` Theodore Ts'o
2015-07-23 17:41     ` Tejun Heo
2015-07-23 18:27 ` [PATCH block/for-linus] block: export bio_associate_*() and wbc_account_io() Tejun Heo
2015-07-23 18:30   ` Chris Mason
2015-07-23 19:36   ` Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2025-07-14 22:22 linux-next: build failure after merge of the ext4 tree 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-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=20150723164953.GA15778@thunk.org \
    --to=tytso@mit.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=tj@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;
as well as URLs for NNTP newsgroup(s).