From: Ingo Molnar <mingo@elte.hu>
To: Adrian Bunk <bunk@kernel.org>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Alexey Starikovskiy <aystarik@gmail.com>,
lenb@kernel.org, astarikovskiy@suse.de,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: [2.6 patch] acpi/battery.c: make 2 functions static
Date: Mon, 3 Mar 2008 13:50:27 +0100 [thread overview]
Message-ID: <20080303125027.GA21577@elte.hu> (raw)
In-Reply-To: <20080303122953.GH4457@cs181133002.pp.htv.fi>
* Adrian Bunk <bunk@kernel.org> wrote:
> I can only repeat that I did state several times on linux-kernel that
> it never worked.
>
> If you consider it my fault that noone reads my emails then you are
> right that it's my fault...
well, i'm trying to assume the best, so please explain the following
sequence of events to me:
1) as you said you knew about this bug - which bug causes more inlining
overhead than hundreds of your uninlining patches combined. The bug
was introduced ~2 years ago in -mm - before the feature hit mainline
in v2.6.16.
2) the fix was really trivial and the intention of the feature was well
understood - but the feature stayed as a NOP in the upstream kernel
for 2 years.
still, while you clearly had interest in this general area of the kernel
(for example you wrote hundreds of tiny uninlining patches that work
towards a similar goal), but strangely at the same time you neither
fixed, nor properly escallated this _far_ bigger bug that causes +2.3%
of text bloat on x86 [more than 120K of kernel text]. In fact:
- you created bugzillas for far smaller bugs in the past, but you never
created a bugzilla for this that i'm aware of.
- you never directly raised this issue with us: "look guys, this thing
really is broken - please reply to me with a fix".
- you never said "this is a regression that should be fixed" to any of
the regression lists.
in other words: for about two years you knew about a bug that should
have been fixed the day after it got introduced.
i obviously cannot know what your intentions were with this conduct, so
i'm eagerly awaiting your explanation for it. Thanks,
Ingo
next prev parent reply other threads:[~2008-03-03 12:50 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-01 16:19 [2.6 patch] acpi/battery.c: make 2 functions static Adrian Bunk
2008-03-01 18:26 ` Alexey Starikovskiy
2008-03-01 18:35 ` Adrian Bunk
2008-03-01 18:42 ` Alexey Starikovskiy
2008-03-01 18:45 ` Adrian Bunk
2008-03-03 8:57 ` Ingo Molnar
2008-03-03 9:13 ` Adrian Bunk
2008-03-03 9:17 ` Ingo Molnar
2008-03-03 9:31 ` Sam Ravnborg
2008-03-03 9:48 ` Adrian Bunk
2008-03-03 10:39 ` Ingo Molnar
2008-03-03 11:34 ` Adrian Bunk
2008-03-03 11:45 ` Ingo Molnar
2008-03-03 12:02 ` Adrian Bunk
2008-03-03 12:10 ` Ingo Molnar
2008-03-03 12:29 ` Adrian Bunk
2008-03-03 12:50 ` Ingo Molnar [this message]
2008-03-03 14:54 ` Adrian Bunk
2008-03-03 15:01 ` Adrian Bunk
2008-03-04 13:16 ` Ingo Molnar
2008-03-04 13:47 ` Adrian Bunk
2008-03-04 14:22 ` Ingo Molnar
2008-03-04 14:36 ` Jörn Engel
2008-03-04 14:45 ` Ingo Molnar
2008-03-03 12:13 ` [patch] x86: phase out forced inlining Ingo Molnar
2008-03-03 14:56 ` Sam Ravnborg
2008-03-04 16:46 ` Ingo Molnar
2008-03-04 18:07 ` Harvey Harrison
2008-03-04 18:09 ` H. Peter Anvin
2008-03-04 18:14 ` Harvey Harrison
2008-03-04 18:18 ` Harvey Harrison
2008-03-03 15:01 ` Arjan van de Ven
2008-03-03 15:58 ` Harvey Harrison
2008-03-04 6:42 ` Andrew Morton
2008-03-04 7:32 ` Ingo Molnar
2008-03-04 8:00 ` Andrew Morton
2008-03-04 9:50 ` Andi Kleen
2008-03-04 8:03 ` Sam Ravnborg
2008-03-04 8:38 ` Andrew Morton
2008-03-03 9:45 ` [2.6 patch] acpi/battery.c: make 2 functions static Adrian Bunk
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=20080303125027.GA21577@elte.hu \
--to=mingo@elte.hu \
--cc=arjan@infradead.org \
--cc=astarikovskiy@suse.de \
--cc=aystarik@gmail.com \
--cc=bunk@kernel.org \
--cc=hpa@zytor.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
/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