linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Jason Wessel <jason.wessel@windriver.com>,
	Martin Hicks <mort@sgi.com>
Subject: Re: linux-next: build failure after merge of the rr tree
Date: Wed, 2 Jun 2010 14:15:16 +0930	[thread overview]
Message-ID: <201006021415.17205.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20100602120345.e530c53b.sfr@canb.auug.org.au>

On Wed, 2 Jun 2010 11:33:45 am Stephen Rothwell wrote:
> Hi Rusty,
> 
> After merging the rr tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
> 
> kernel/debug/kdb/kdb_main.c: In function 'kdb_lsmod':
> kernel/debug/kdb/kdb_main.c:1897: error: 'struct module' has no member named 'modules_which_use_me'
> kernel/debug/kdb/kdb_main.c:1897: error: 'struct module' has no member named 'modules_which_use_me'

Thanks Stephen! I'm not surprised Linus (and I) missed this.

Jason/Martin, please don't do this again.  If you need a structure definition
from a file, pull it out into the header don't cut and paste it like
kernel/debug/kdb/kdb_main.c line 1859:

	#if defined(CONFIG_MODULES)
	/* modules using other modules */
	struct module_use {
		struct list_head list;
		struct module *module_which_uses;
	};

I've fixed this as part of the Linus-inspired module locking cleanup which
should hit linux-next tomorrow and -rc2 sometime.

Thanks,
Rusty.

  reply	other threads:[~2010-06-02  4:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-02  2:03 linux-next: build failure after merge of the rr tree Stephen Rothwell
2010-06-02  4:45 ` Rusty Russell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-12-20  2:39 Stephen Rothwell
2011-12-20  3:54 ` Rusty Russell
2011-08-30  4:03 Stephen Rothwell
2011-08-31  4:36 ` Rusty Russell
2011-02-09  2:01 Stephen Rothwell
2011-02-09  2:13 ` Rusty Russell
2011-02-09  8:36   ` Dmitry Torokhov
2011-01-19  4:42 Stephen Rothwell
2011-01-19  9:59 ` Rusty Russell
2011-01-19 10:05   ` Linus Walleij
2011-01-19 10:04 ` Linus Walleij
2010-08-04  2:15 Stephen Rothwell
2010-06-01  3:11 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=201006021415.17205.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=jason.wessel@windriver.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mort@sgi.com \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.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).