linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roman Zippel <zippel@linux-m68k.org>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: Sam Ravnborg <sam@ravnborg.org>,
	Jan Engelhardt <jengelh@linux01.gwdg.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Section mismatch warnings
Date: Mon, 26 Jun 2006 14:37:19 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0606261425340.17704@scrub.home> (raw)
In-Reply-To: <20060623222346.GC27946@ftp.linux.org.uk>

Hi,

On Fri, 23 Jun 2006, Al Viro wrote:

> On Sat, Jun 24, 2006 at 12:12:18AM +0200, Sam Ravnborg wrote:
> > All the .smp_locks related warnings are gone when I get the kbuild.git
> > tree pushed linus wise. Needs to spend only an hour or so before it is
> > ready and will do so during the weekend.
> 
> Another fun toy that might be interesting there:
> 
> >From nobody Mon Sep 17 00:00:00 2001
> From: Al Viro <viro@zeniv.linux.org.uk>
> Date: Fri, 26 May 2006 08:35:22 -0400
> Subject: [PATCH] add make listconfig (show all kconfig symbols seen by parser)

I don't mind the functionality, but what I'd like to avoid is adding lots 
of little config targets, so what I'd like to add is something more like 
'make queryconfig', which maybe even could be extended to some simple 
scripting functionality.

> +static void list_symbols(struct menu *m)
> +{
> +	for (m = m->list; m; m = m->next) {
> +		struct symbol *s = m->sym;
> +		if (s && !sym_is_choice(s)) {

for_all_symbols() would be simpler and avoids possible duplicate menu 
entries and I think it's better to just test for s->name.

bye, Roman

  reply	other threads:[~2006-06-26 12:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-23 17:40 Section mismatch warnings Jan Engelhardt
2006-06-23 22:12 ` Sam Ravnborg
2006-06-23 22:22   ` Al Viro
2006-06-24 21:02     ` Sam Ravnborg
2006-06-23 22:23   ` Al Viro
2006-06-26 12:37     ` Roman Zippel [this message]
2007-07-30 17:48 Gabriel C
2007-07-30 18:51 ` Sam Ravnborg
2007-07-30 19:31   ` Gabriel C
2007-07-31 19:45     ` Gabriel C
2007-07-31 20:48       ` Sam Ravnborg
2007-07-31 21:58         ` Gabriel C
2007-08-02 14:27           ` Gabriel C
2007-08-02 16:31             ` Sam Ravnborg
2007-08-02 17:12               ` Gabriel C
2007-08-02 17:59                 ` Sam Ravnborg
2007-08-02 18:24                   ` Gabriel C

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=Pine.LNX.4.64.0606261425340.17704@scrub.home \
    --to=zippel@linux-m68k.org \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=viro@ftp.linux.org.uk \
    /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).