linux-kernel - Re: 2.6.20-rc6-mm3

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 06 Feb 2007 18:46:55 -0800
From:	Daniel Walker <dwalker@...sta.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org
Subject: Re: 2.6.20-rc6-mm3

I guess I will respond ....

On Wed, 2007-02-07 at 00:51 +0100, Ingo Molnar wrote:
> * Daniel Walker <dwalker@...sta.com> wrote:
> 
> > > | If we change the current "timer" entry to be listed as 
> > > | "lapic-timer" and not "IO-APIC-edge" (or one of the other names) 
> > > | and replace it with the count from LOC
> > > 
> > > this is a pretty clear sentence, i dont think i misunderstood 
> > > anything about it. If i did, please point it out specifically.
> > 
> > Geez , man I've corrected this statement already .. [...]
> 
> i'm sorry, but where did you "correct this statement already"? You 
> havent replied to your mail to correct it explicitly, and there's no 
> later statement of yours that says anything near to "let me correct this 
> via X" or "i was wrong here, i meant Y".

I know that you see corrections as responses to your own email, but it's
not universal .. Everyone has their own methodology, AFAIK it's free
form ..

> the only subsequent reference of yours seems to be:
> 
> | I'm not saying we should "fake" anything .. I'm saying list what's 
> | really happening .. In a human readable way .
> 
> what you write here does not read as a 'correction', this disputes my 
> characterisation, suggesting that your original point is still intact. 
> How should i have known that you meant this to be a 'correction' of your 
> original point, and that this (whatever it means precisely) replaces it?
> 
> if you concede a point or correct a statement then /please/ make it 
> clear. There's nothing bad about being wrong or being stupid 
> occasionally, it happens to all of us.

I don't take a literal approach to email, which you seem to be taking ..
I think your seeing this thread as an argument for or against something
and you have taken a position which you diligently stick to..

My position is not fixed. However, your arguing as if my position was
fixed. My perspective of this thread was not to argue for a specific
change, but to throw out changes and see if anything stuck ..

Where my statements were suppose to be loose to begin with, so loose as
to only spark the start of an idea, not to promote something specific.
If you read the start of the thread you'll notice that I gave Thomas two
totally opposite ideas.

"We could just remove the timer entry."
or
"[..]how about adding the interrupts to the list which are driving the
timer ?"

When I started the thread I had a similar position as Thomas, but I was
concerned that I was missing something or the code was missing
something.. This was the reason for starting the thread ..

So I'll gladly concede all points. To me it wasn't about the argument,
or even my own ideas ..

Daniel

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/