From: Russell King <rmk+lkml@arm.linux.org.uk>
To: "David S. Miller" <davem@davemloft.net>
Cc: jgarzik@pobox.com, bunk@stusta.de, saw@saw.sw.com.sg,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [RFC: 2.6 patch] remove drivers/net/eepro100.c
Date: Wed, 23 Nov 2005 22:53:19 +0000 [thread overview]
Message-ID: <20051123225319.GP15449@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20051123.143946.41188551.davem@davemloft.net>
On Wed, Nov 23, 2005 at 02:39:46PM -0800, David S. Miller wrote:
> From: Russell King <rmk+lkml@arm.linux.org.uk>
> Date: Wed, 23 Nov 2005 22:15:48 +0000
>
> > I leave it up to you how to proceed. Effectively I'm now completely
> > out of the loop on this with no hardware to worry about. Sorry.
> >
> > Finally, please don't assign any blame for this in my direction; I
> > reported it and I kept bugging people about it, and in spite of my
> > best efforts there was very little which was forthcoming. Obviously
> > that wasn't enough.
>
> I think you're being unreasonable.
I think you're being unreasonable telling me that I'm being unreasonable.
> They've worked on a fix for the problem, and now you're unable to test
> the fix, and you're angry at them because they took so long to code up
> the fix.
>
> If you're overextended and have too much work to do and that's
> stressing you out, that doesn't give you permission to take it
> out on other people.
No. It's quite simple.
I've worked on trying to replicate the problem today. Tomorrow I'm
out at a meeting and since I'm no longer working on the problematical
hardware, it is being returned.
That means there's about 15 minutes left before I go to sleep before
having to be up early tomorrow to go on a 2 hour journey to attend a
meeting. What do you want me to do with those 15 minutes? Perform a
miracle maybe?
David, I ask you to retract your unreasonable mail. I'm being quite
calm here. I'm just pointing out the facts that as of *now* I'm no
longer in a position to test.
I was rather hoping that being crystal clear about the reasons about
_why_ I'm no longer able to continue participating in his problem
that I would be seen not to be unreasonable.
I guess I'm just cursed.
Sorry.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2005-11-23 22:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 3:33 [RFC: 2.6 patch] remove drivers/net/eepro100.c Adrian Bunk
2005-11-18 9:01 ` Russell King
2005-11-18 9:08 ` David S. Miller
2005-11-18 16:12 ` Jeff Garzik
2005-11-18 16:32 ` Russell King
2005-11-19 20:34 ` Adrian Bunk
2005-11-23 22:15 ` Russell King
2005-11-23 22:24 ` Russell King
2005-11-24 10:30 ` Catalin Marinas
2005-11-23 22:39 ` David S. Miller
2005-11-23 22:53 ` Russell King [this message]
2005-11-23 23:01 ` David S. Miller
2005-11-18 17:04 ` Tim Schmielau
-- strict thread matches above, loose matches on Subject: below --
2006-01-05 18:18 Adrian Bunk
2006-01-05 18:57 ` Jeff Garzik
2006-01-05 21:04 ` Lennert Buytenhek
2006-01-15 0:43 ` Adrian Bunk
2006-01-15 13:19 ` Vitaly Bordug
2006-01-16 0:03 ` Stephen Hemminger
2006-01-17 18:48 ` Adrian Bunk
2006-01-17 22:27 ` John Ronciak
2006-01-18 0:32 ` John W. Linville
2006-01-18 0:36 ` Jeff Garzik
2006-01-18 10:34 ` Vitaly Bordug
2006-01-16 0:08 ` 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=20051123225319.GP15449@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=bunk@stusta.de \
--cc=davem@davemloft.net \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=saw@saw.sw.com.sg \
/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;
as well as URLs for NNTP newsgroup(s).