From: Pavel Machek <pavel@suse.cz>
To: Brent Casavant <bcasavan@sgi.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH 0/2] external interrupts
Date: Sun, 21 Aug 2005 00:21:59 +0200 [thread overview]
Message-ID: <20050820222159.GP516@openzaurus.ucw.cz> (raw)
In-Reply-To: <20050819160716.U87000@chenjesu.americas.sgi.com>
Hi!
> Here is a set of patches that implements an external interrupt capability
> in Linux, along with a device driver for a specific hardware device. I
> submitted the patches several weeks ago, and they drew no comments, which
> I take to be a good sign. Anyway, I'm
It was not good sign in this particular case. My reaction was "this is _so_
overengineered tjat he's probably joking".
Pavel
--
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
next prev parent reply other threads:[~2005-08-21 14:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-19 21:55 Brent Casavant
2005-08-20 22:21 ` Pavel Machek [this message]
2005-08-22 21:27 ` Brent Casavant
2005-08-22 21:43 ` Andrew Morton
2005-08-22 22:17 ` Brent Casavant
2005-08-23 9:57 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2005-07-28 21:13 Brent Casavant
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=20050820222159.GP516@openzaurus.ucw.cz \
--to=pavel@suse.cz \
--cc=akpm@osdl.org \
--cc=bcasavan@sgi.com \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome