From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ulf Samuelsson Date: Sat, 21 Jul 2007 00:15:32 +0200 Subject: [Buildroot] svn commit: trunk/buildroot/target: linux-experimental References: <20070720112745.D7AD5A680F@busybox.net> <20070720134836.GA29640@real.realitydiluted.com> Message-ID: <043e01c7cb1e$445dbdc0$dcc4af0a@atmel.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net > On Fri, Jul 20, 2007 at 04:27:45AM -0700, ulf at uclibc.org wrote: >> Author: ulf >> Date: 2007-07-20 04:27:45 -0700 (Fri, 20 Jul 2007) >> New Revision: 19179 >> >> Log: >> Add experimental linux target option >> >> Added: >> trunk/buildroot/target/linux-experimental/ >> trunk/buildroot/target/linux-experimental/Makefile.in >> >> Modified: >> trunk/buildroot/target/Makefile.in >> > I wish you would have done a RFC for this before committing as I would > have rejected it. You are adding more complexity and more configuration > options to the system. If people want to do something special with their > Linux kernel, they should handle it in their own target specific > directory and override the variables LINUX_HEADERS_VERSION, LINUX26_DIR, > LINUX26_KCONFIG, LINUX26_BINLOC, etc. I have no problem making the Linux configuration a part of the target/device/Atmel directory, but then the target/linux needs to be disabled if an Atmel chip is selected in order to avoid conflicts. I do have a problem with having people editing configuration files which can easily be handled by the config system. > Please revert this patch. Also, > even if it were to stay in, you provided no documentation again. The idea was basically to let people try this out, and there was never any plan to keep this for a long time. I expect that it will be gone within a week or so. > > -Steve > Best Regards Ulf Samuelsson