linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jan Kara <jack@suse.cz>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	reiserfs-devel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the ext3 tree
Date: Mon, 2 Jan 2012 23:40:12 +0100	[thread overview]
Message-ID: <20120102224012.GE3626@quack.suse.cz> (raw)
In-Reply-To: <20111228112254.551c2ee5a1ac8509962d6611@canb.auug.org.au>

  Hi,

On Wed 28-12-11 11:22:54, Stephen Rothwell wrote:
> After merging the ext3 tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
> 
> fs/reiserfs/super.c: In function 'reiserfs_show_options':
> fs/reiserfs/super.c:652:20: error: 'struct reiserfs_sb_info' has no member named 's_qf_names'
> fs/reiserfs/super.c:653:50: error: 'struct reiserfs_sb_info' has no member named 's_qf_names'
> fs/reiserfs/super.c:656:20: error: 'struct reiserfs_sb_info' has no member named 's_qf_names'
> fs/reiserfs/super.c:657:50: error: 'struct reiserfs_sb_info' has no member named 's_qf_names'
> fs/reiserfs/super.c:660:20: error: 'struct reiserfs_sb_info' has no member named 's_jquota_fmt'
> fs/reiserfs/super.c:661:21: error: 'struct reiserfs_sb_info' has no member named 's_jquota_fmt'
> fs/reiserfs/super.c:663:26: error: 'struct reiserfs_sb_info' has no member named 's_jquota_fmt'
> 
> Caused by commit 5fa84b871b97 ("reiserfs: Properly display mount options
> in /proc/mounts").  Hint: CONFIG_QUOTA is not set in this build.
  Ah, stupid me. Fixed now. Thanks for letting me know.

									Honza
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

  reply	other threads:[~2012-01-02 22:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-28  0:22 linux-next: build failure after merge of the ext3 tree Stephen Rothwell
2012-01-02 22:40 ` Jan Kara [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-03-07  0:07 Stephen Rothwell
2024-03-07  6:18 ` Winston Wen
2024-03-07 12:03   ` Jan Kara
2023-08-16  0:37 Stephen Rothwell
2020-11-12 23:47 Stephen Rothwell
2020-11-13 10:33 ` Jan Kara
2019-01-31  4:14 Stephen Rothwell
2019-01-31 10:11 ` Jan Kara
2019-01-31 22:09   ` Stephen Rothwell
2014-08-08  1:52 Stephen Rothwell
2014-08-08  9:22 ` Jan Kara
2010-03-02  0:36 Stephen Rothwell
2010-03-02  9:07 ` Christoph Hellwig
2010-03-02 17:27 ` Jan Kara
2010-03-03  0:42   ` 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=20120102224012.GE3626@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=reiserfs-devel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).