All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Benjamin Poirier <bpoirier@suse.de>
Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
	linux-kbuild@vger.kernel.org, Arnaud Lacombe <lacombar@gmail.com>
Subject: Re: [menuconfig] build failure.
Date: Fri, 19 Oct 2012 17:17:31 +0200	[thread overview]
Message-ID: <50816F0B.7040001@suse.cz> (raw)
In-Reply-To: <20121016125821.GA997@d2.synalogic.ca>

On 16.10.2012 14:58, Benjamin Poirier wrote:
> Michal, do you think we're better off:
> * copying the CIRCLEQ macros from sys/queue.h (about 30 lines needed,
>   bsd licenced)
> * switching over to kernel-style linked lists using:
> 	* a copy of tools/firewire/list.h
> 	* #include "../../../include/linux/list.h" like perf does in
> 	  tools/perf/util/include/linux/list.h

I did not know that linux/list.h can be used by userspace without
modifications. But I guess such dependency would still be inconvenient
for people who are using kconfig externally. Arnaud, what do you think?
So I think that the next-best thing is to copy tools/firewire/list.h.
That way, we avoid all the ifdefs.

Michal

  parent reply	other threads:[~2012-10-19 15:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201210162049.HIC43747.OOtOJHFFFQMVSL@I-love.SAKURA.ne.jp>
2012-10-16 12:58 ` [menuconfig] build failure Benjamin Poirier
2012-10-17 22:47   ` Yann E. MORIN
2012-10-19 14:46   ` Tetsuo Handa
2012-10-19 15:17   ` Michal Marek [this message]
2012-10-16 13:46 ` [PATCH 3.7-rc1] Fix kconfig failure on old environments Tetsuo Handa

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=50816F0B.7040001@suse.cz \
    --to=mmarek@suse.cz \
    --cc=bpoirier@suse.de \
    --cc=lacombar@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.