mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: barebox@lists.infradead.org
Subject: Re: [PATCH 09/11] kbuild: generate lexer and parser during build instead of shipping
Date: Mon, 31 Dec 2018 10:02:17 +0900	[thread overview]
Message-ID: <CAK7LNARozoFKvkegkCUvs88_XppEL93gAmZyW5y9p-bkHounjg@mail.gmail.com> (raw)
In-Reply-To: <1546178368-26182-10-git-send-email-yamada.masahiro@socionext.com>

On Sun, Dec 30, 2018 at 11:01 PM Masahiro Yamada
<yamada.masahiro@socionext.com> wrote:
>
> Recent kernel versions run flex and bison to generate lexers and
> parsers from real source files such as *.l and *.y . This provides
> better maintainability than version-controlling pre-generated C files
> with a "_shipped" suffix.
>
> This commit imports from flex and bison rules form Linux, and delete
> pre-generated parsers and lexers.


Please let me rephrase this paragraph as follows:

This commit imports flex and bison rules from Linux, and deletes
pre-generated parsers and lexers.






> Refer to the following commits in Linux:
>
>  - 033dba2ec06c ("kbuild: prepare to remove C files pre-generated by
>    flex and bison")
>
>  - 29c833061c1d ("kconfig: generate lexer and parser during build
>    instead of shipping")
>
>  - e039139be8c2 ("scripts/dtc: generate lexer and parser during
>    build instead of shipping")
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>


-- 
Best Regards
Masahiro Yamada

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2018-12-31  1:03 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-30 13:59 [PATCH 00/11] Sync Kconfig to Linux 4.20 Masahiro Yamada
2018-12-30 13:59 ` [PATCH 01/11] kbuild: filter-out PHONY targets from "targets" Masahiro Yamada
2018-12-30 13:59 ` [PATCH 02/11] kbuild: add .DELETE_ON_ERROR special target Masahiro Yamada
2018-12-31  5:52   ` Sam Ravnborg
2018-12-30 13:59 ` [PATCH 03/11] kbuild: add .SECONDARY " Masahiro Yamada
2018-12-31  5:55   ` Sam Ravnborg
2018-12-30 13:59 ` [PATCH 04/11] kbuild: add %.lex.c and %.tab.[ch] to 'targets' automatically Masahiro Yamada
2018-12-31  5:55   ` Sam Ravnborg
2018-12-30 13:59 ` [PATCH 05/11] treewide: remove blank texts Masahiro Yamada
2018-12-30 13:59 ` [PATCH 06/11] .gitignore: move *.lex.c *.tab.[ch] patterns to the top-level .gitignore Masahiro Yamada
2018-12-30 13:59 ` [PATCH 07/11] kbuild: clean up *.lex.c and *.tab.[ch] patterns from top-level Makefile Masahiro Yamada
2018-12-30 13:59 ` [PATCH 08/11] kbuild: rename HOSTLOADLIBES_* to HOSTLDLIBS_* Masahiro Yamada
2018-12-30 13:59 ` [PATCH 09/11] kbuild: generate lexer and parser during build instead of shipping Masahiro Yamada
2018-12-31  1:02   ` Masahiro Yamada [this message]
2018-12-30 13:59 ` [PATCH 10/11] kconfig: sync to Linux 4.20 Masahiro Yamada
2018-12-30 13:59 ` [PATCH 11/11] kbuild: remove unnecessary LEX_PREFIX and YACC_PREFIX Masahiro Yamada
2018-12-31  6:12 ` [PATCH 00/11] Sync Kconfig to Linux 4.20 Sam Ravnborg
2019-01-01  9:13   ` Masahiro Yamada
2019-01-03  9:18     ` Sascha Hauer

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=CAK7LNARozoFKvkegkCUvs88_XppEL93gAmZyW5y9p-bkHounjg@mail.gmail.com \
    --to=yamada.masahiro@socionext.com \
    --cc=barebox@lists.infradead.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