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: Tue, 4 Mar 2008 15:22:48 +0100 [thread overview]
Message-ID: <20080304142248.GA2201@elte.hu> (raw)
In-Reply-To: <20080304134701.GA20278@cs181133002.pp.htv.fi>
* Adrian Bunk <bunk@kernel.org> wrote:
> On Tue, Mar 04, 2008 at 02:16:00PM +0100, Ingo Molnar wrote:
> >
> > * Adrian Bunk <bunk@stusta.de> wrote:
> >
> > > > 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.
> > >
> > > I don't remember having ever said this.
> > >
> > > Your choices are:
> > > [ ] prove your accusation that I said I
> > > "knew about this bug before the feature hit mainline"
> > > [ ] apologize
> > > [ ] be the firest person ever in my killfile
> >
> > Adrian, you must be misunderstanding something. Where exactly in the
> > above sentences do i assert that you "knew about this bug before the
> > feature hit mainline"? I dont say that and cannot say that -
>
> Please explain your statement "before the feature hit mainline in
> v2.6.16" in the above sentence of you in a reasonable way other than
> that it should say I knew about it before the feature hit mainline.
do you mean this paragraph:
| 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.
sorry, but i know of no rule of grammar that could read your
interpretation into my two sentences.
(and that's not surprising at all, because i never intended to even
suggest that you knew about this breakage "before it went mainline" -
why would i even care about such a detail?)
Ingo
next prev parent reply other threads:[~2008-03-04 14:23 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
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 [this message]
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=20080304142248.GA2201@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