All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaud Lacombe <lacombar@gmail.com>
To: Michal Marek <mmarek@suse.cz>
Cc: linux-kbuild@vger.kernel.org, David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [RFCv2 00/13] Kbuild: factor parser rules
Date: Tue, 24 May 2011 10:18:00 -0400	[thread overview]
Message-ID: <BANLkTiknMSzx9yS5zrUnwtXzMPoe34G4tQ@mail.gmail.com> (raw)
In-Reply-To: <4DDB8CB4.2090701@suse.cz>

Hi,

2011/5/24 Michal Marek <mmarek@suse.cz>:
> On 23.5.2011 10:10, Arnaud Lacombe wrote:
>>
>> Hi,
>>
>> [ Original RFC and motivation can be found at:
>> http://marc.info/?l=linux-kbuild&m=130456101131801&w=2 ]
>>
>> I tried to re-think the order in this serie to address Michal comments.
>>
>> Main changes since v1 are:
>>  - include scripts/dtc/' parser in the scope of the patchset
>>  - do not rename any parser source
>>  - make lexer file name consistent, ie. name it %.lex.c, not lex.%.c
>>  - rebase on top of v2.6.39
>>
>> A few notes:
>>  - the parser should not include the lexer; however, this has the
>> advantage to
>>    avoid having to deals with the parser's header.
>>  - the tuple ( "migrate parser to implicit rules", regen parser) should
>> really
>>    be one commit, to enforce bisect'ability
>>
>> Comments welcome!
>>  - Arnaud
>
> Hi,
>
> thanks for the series, but I will probably not have time to review it before
> this merge window closes. So it will have to wait for .41 most likely.
>
fine with me, I am not entirely happy with that serie anyway, so I'll
certainly do another iteration after -rc1 (to include whatever has
changed in the mean time).

 - Arnaud

  reply	other threads:[~2011-05-24 14:18 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-23  8:10 [RFCv2 00/13] Kbuild: factor parser rules Arnaud Lacombe
2011-05-23  8:10 ` [RFCv2 01/13] kbuild: add implicit rules for parser generation Arnaud Lacombe
2011-05-23  8:10 ` [RFCv2 02/13] genksyms: include the lexer from the parser Arnaud Lacombe
2011-05-23  8:10 ` [RFCv2 03/13] genksyms: pass hash and lookup functions name and target language though the input file Arnaud Lacombe
2011-05-23  8:10 ` [RFCv2 04/13] genksyms: migrate parser to implicit rules Arnaud Lacombe
2011-05-23  8:10 ` [RFCv2 05/13] genksym: regen parser Arnaud Lacombe
2011-05-23  8:10 ` [RFCv2 06/13] kconfig: constify `kconf_id_lookup' Arnaud Lacombe
2011-05-23  8:10 ` [RFCv2 07/13] kconfig: back-out parser prefix, from `zconf' to `yy' Arnaud Lacombe
2011-05-23  8:54   ` Yann E. MORIN
2011-05-23  9:07     ` Arnaud Lacombe
2011-05-23  8:10 ` [RFCv2 08/13] kconfig: kill no longer needed reference to YYDEBUG Arnaud Lacombe
2011-05-23  8:10 ` [RFCv2 09/13] kconfig: migrate parser to implicit rules Arnaud Lacombe
2011-05-23  8:10 ` [RFCv2 10/13] kconfig: regen parser Arnaud Lacombe
2011-05-23  8:10 ` [RFCv2 11/13] dtc: include the lexer from the parser Arnaud Lacombe
2011-05-23  8:10 ` [RFCv2 12/13] dtc: migrate parser to implicit rules Arnaud Lacombe
2011-05-23  8:10 ` [RFCv2 13/13] dtc: regen parser Arnaud Lacombe
2011-05-23  8:39 ` [RFCv2 00/13] Kbuild: factor parser rules Arnaud Lacombe
2011-05-24 10:47 ` Michal Marek
2011-05-24 14:18   ` Arnaud Lacombe [this message]
2011-06-03 17:16 ` [RFCv3] " Arnaud Lacombe
2011-06-07 15:29   ` Michal Marek
2011-06-07 15:52     ` Arnaud Lacombe
2011-06-07 20:52     ` [RFCv4] " Arnaud Lacombe
2011-06-07 21:27       ` Arnaud Lacombe
2011-06-08  5:03       ` [RFCv5] " Arnaud Lacombe
2011-06-08 15:38         ` Michal Marek
2011-06-08 16:11           ` Arnaud Lacombe
2011-06-08 20:34             ` Michal Marek
2011-06-08 21:10               ` Arnaud Lacombe
2011-06-09 12:09                 ` Michal Marek
2011-06-09 18:16                   ` Arnaud Lacombe
2011-06-23 21:07                     ` 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=BANLkTiknMSzx9yS5zrUnwtXzMPoe34G4tQ@mail.gmail.com \
    --to=lacombar@gmail.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=mmarek@suse.cz \
    /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.