From: Michal Marek <mmarek@suse.cz>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: linux-kbuild@vger.kernel.org,
Benjamin Poirier <benjamin.poirier@gmail.com>,
Jean Sacren <sakiwit@gmail.com>,
Arnaud Lacombe <lacombar@gmail.com>,
Wang YanQing <udknight@gmail.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Davidlohr Bueso <dave@gnu.org>,
linux-kernel@vger.kernel.org,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Yaakov Selkowitz <yselkowitz@users.sourceforge.net>
Subject: Re: [PATCH v2] menuconfig: Replace CIRCLEQ by list_head-style lists.
Date: Thu, 25 Oct 2012 15:34:07 +0200 [thread overview]
Message-ID: <50893FCF.5030800@suse.cz> (raw)
In-Reply-To: <201210222138.25805.yann.morin.1998@free.fr>
On 22.10.2012 21:38, Yann E. MORIN wrote:
> Benjamin, Michal, All,
>
> On Sunday 21 October 2012 Benjamin Poirier wrote:
>> From: Benjamin Poirier <bpoirier@suse.de>
>>
>> sys/queue.h and CIRCLEQ in particular have proven to cause portability
>> problems (reported on Debian Sarge, Cygwin and FreeBSD)
>
> Benjamin,
>
> Thank you for working on this! :-)
Yeah, thanks!
>>
>> Changes v1-v2:
>> * integrate the patch/suggestion from Yann to fix problems related to the
>> usage of list.h with xconfig/c++
>> * "new" keyword
>> * offsetof redefinition
>> * silly #endif placement mistake
>
> Michal,
>
> Any more comments on this patch?
>
> If not, then I would suggest to push it for inclusion before 3.7 is released
> (I believe it can go in, as it is a bugfix, not a new feature).
I pushed it to kbuild.git#rc-fixes now and will send it to Linus for 3.7
inclusion later.
Michal
next prev parent reply other threads:[~2012-10-25 13:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1350754935-20014-1-git-send-email-benjamin.poirier@gmail.com>
2012-10-21 9:27 ` [PATCH v2] menuconfig: Replace CIRCLEQ by list_head-style lists Benjamin Poirier
2012-10-22 19:38 ` Yann E. MORIN
2012-10-25 13:34 ` Michal Marek [this message]
2012-11-11 16:02 ` Yann E. MORIN
2012-11-12 12:26 ` Willy Tarreau
2012-11-12 13:35 ` Michal Marek
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=50893FCF.5030800@suse.cz \
--to=mmarek@suse.cz \
--cc=benjamin.poirier@gmail.com \
--cc=dave@gnu.org \
--cc=lacombar@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=sakiwit@gmail.com \
--cc=udknight@gmail.com \
--cc=yann.morin.1998@free.fr \
--cc=yselkowitz@users.sourceforge.net \
/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.