public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	Ulf Magnusson <ulfalizer@gmail.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Nicholas Piggin <npiggin@gmail.com>,
	Kate Stewart <kstewart@linuxfoundation.org>,
	Markus Heiser <markus.heiser@darmarit.de>,
	"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
	Borislav Petkov <bp@suse.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Jonathan Corbet <corbet@lwn.net>,
	Michal Marek <michal.lkml@markovi.net>,
	SeongJae Park <sj38.park@gmail.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Philippe Ombredanne <pombredanne@nexb.com>,
	Max Filippov <jcmvbkbc@gmail.com>
Subject: Re: [PATCH 0/3] kbuild,kconfig: generate lexer/parser C files instead of copying _shipped files
Date: Fri, 15 Dec 2017 20:50:59 +0100	[thread overview]
Message-ID: <20171215195059.GA10168@ravnborg.org> (raw)
In-Reply-To: <CAK7LNAROtWVcpwpaKYAyr=jpPrOu3iMHVCJcVN+4SVp6ZtEd5g@mail.gmail.com>

Hi Masahiro.

> > In Linux build system convention, pre-generated files are version-
> > controlled with a "_shipped" suffix.  During the kernel building,
> > they are simply shipped (copied) removing the suffix.
> >
> > From users' point of view, this approach can reduce external tool
> > dependency for the kernel build,
> >
> > From developers point of view, it is tedious to manually regenerate
> > such artifacts.  In fact, we see several patches to regenerate
> > _shipped files.  They are noise commits.
...

Nice cleanup we should have does years ago.
When we introduced this we did this to minimize the time
it took to configure a clean kernel - as one of the reasons.
Since then the average computer has been significantly faster
so the time to run flex/bison is not an issue anymore.

	Sam

      reply	other threads:[~2017-12-15 19:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-09 16:02 [PATCH 0/3] kbuild,kconfig: generate lexer/parser C files instead of copying _shipped files Masahiro Yamada
2017-12-09 16:02 ` [PATCH 1/3] kbuild: add LEX and YACC variables Masahiro Yamada
2017-12-09 16:02 ` [PATCH 2/3] kbuild: prepare to remove C files pre-generated by flex and bison Masahiro Yamada
2017-12-09 16:47   ` Randy Dunlap
2017-12-14 23:54 ` [PATCH 0/3] kbuild,kconfig: generate lexer/parser C files instead of copying _shipped files Masahiro Yamada
2017-12-15 19:50   ` Sam Ravnborg [this message]

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=20171215195059.GA10168@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=bp@suse.de \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=jcmvbkbc@gmail.com \
    --cc=kstewart@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus.heiser@darmarit.de \
    --cc=mchehab@kernel.org \
    --cc=michal.lkml@markovi.net \
    --cc=npiggin@gmail.com \
    --cc=pombredanne@nexb.com \
    --cc=sj38.park@gmail.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=ulfalizer@gmail.com \
    --cc=yamada.masahiro@socionext.com \
    /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