From: boris@alien8.de
To: "Arnaud Lacombe" <lacombar@gmail.com>
Cc: "Sam Ravnborg" <sam@ravnborg.org>,
"Américo Wang" <xiyou.wangcong@gmail.com>,
"Michal Marek" <mmarek@suse.cz>,
valdis.kletnieks@vt.edu, bp@alien8.de,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
davej@redhat.com
Subject: Re: [PATCH] kbuild: Allow to combine multiple W= levels
Date: Mon, 2 May 2011 20:03:05 +0200 (CEST) [thread overview]
Message-ID: <2b5d75ba05bd7889ac80514015e36ad2.squirrel@www.skyhub.de> (raw)
In-Reply-To: <BANLkTi==Tx6sXcA2Bk6Cp7wc1DY-7c1V3g@mail.gmail.com>
I'm really getting tired of this!
> Because you are not even sure of what you submitted is good for the kernel
> ?
No, because we need to get a feeling of what makes sense for all these
options first. I'd rather do the learning-by-doing thing here and
implement what makes sense than braindead frameworks.
> I think this has been done completely wrong, first all the extra
> warnings got in (without a detailed impact implied by each one),
WTF? http://marc.info/?l=linux-kbuild&m=130346037604547&w=2
No one else did check those and said, ACK/NACK so we went in with this
initial splitting first.
> then it was decided to be split in several level (which I proposed on
> Feb 20th, but was originally rejected by Borislav Petkov),
Of course, because it made no sense at the time. Sam added it later with
his proposal patch.
> then, well, some may need to be removed because they are not good for
> Linux.
have you even tried all those options and come up with concrete
suggestions on which options should go in and which shouldn't, and for
what reasons? I don't think so. So until you do, I don't care what you
have to say.
[snip a bunch of bullshit]
> Now, the drawback of your comment is that when it will be time to
> change the interface, some will object because it will have been
> started to be used by third party scripts, and as authors of third
> party script, it is a PITA to have to check the kernel version to know
> if I should W=1,2,3, or W=123 or if W=3 includes W=1 ...
This is exactly why we're trying to get a feeling of this by _running_
it and _then_ _bitching_ about it. And this is for DEVELOPERS only - if
they've introduced it in their scripts, then they should be able to fix
any changes very easily.
next prev parent reply other threads:[~2011-05-02 18:03 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 21:39 [RFC PATCH] kbuild: implement several " Sam Ravnborg
2011-04-21 21:58 ` Joe Perches
2011-04-21 22:56 ` Stratos Psomadakis
2011-04-21 22:06 ` Stratos Psomadakis
2011-04-22 1:28 ` Sam Ravnborg
2011-04-22 7:38 ` [RFC PATCH v2] " Sam Ravnborg
2011-04-22 8:19 ` [RFC PATCH] " Borislav Petkov
2011-04-22 10:15 ` Sam Ravnborg
2011-04-22 10:20 ` Borislav Petkov
2011-04-22 10:46 ` [PATCH v3] " Borislav Petkov
2011-04-22 11:09 ` Sam Ravnborg
2011-04-22 17:50 ` [PATCH v3.1] " Borislav Petkov
2011-04-26 19:52 ` Michal Marek
2011-04-26 20:43 ` Borislav Petkov
2011-04-27 8:22 ` Sam Ravnborg
2011-04-27 8:25 ` Sam Ravnborg
2011-04-27 11:35 ` Borislav Petkov
2011-04-27 20:15 ` [PATCH v3.2] " Borislav Petkov
2011-04-27 20:21 ` Joe Perches
2011-04-27 20:46 ` Sam Ravnborg
2011-04-27 20:46 ` Sam Ravnborg
2011-04-28 16:18 ` Michal Marek
2011-04-28 0:25 ` [PATCH v3.1] " Valdis.Kletnieks
2011-04-28 16:24 ` Michal Marek
2011-04-28 17:59 ` Valdis.Kletnieks
2011-04-29 13:31 ` [PATCH] kbuild: Allow to combine multiple " Michal Marek
2011-04-29 17:43 ` Sam Ravnborg
2011-04-29 18:13 ` Arnaud Lacombe
2011-04-29 18:27 ` Valdis.Kletnieks
2011-04-29 18:29 ` Valdis.Kletnieks
2011-05-02 15:38 ` Michal Marek
2011-05-02 15:53 ` Arnaud Lacombe
2011-05-02 16:05 ` Michal Marek
2011-05-02 16:17 ` Arnaud Lacombe
2011-05-02 16:16 ` Américo Wang
2011-05-02 17:07 ` Sam Ravnborg
2011-05-02 17:34 ` Arnaud Lacombe
2011-05-02 18:03 ` boris [this message]
2011-05-02 18:45 ` Arnaud Lacombe
2011-05-02 18:51 ` boris
2011-05-02 20:35 ` Michal Marek
2011-04-27 8:27 ` [PATCH v3] kbuild: implement several " Geert Uytterhoeven
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=2b5d75ba05bd7889ac80514015e36ad2.squirrel@www.skyhub.de \
--to=boris@alien8.de \
--cc=bp@alien8.de \
--cc=davej@redhat.com \
--cc=lacombar@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=sam@ravnborg.org \
--cc=valdis.kletnieks@vt.edu \
--cc=xiyou.wangcong@gmail.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
all inboxes | Powered by JetHome®