From: "Frank Ch. Eigler" <fche@redhat.com>
To: Robert Shideleff <bigbob@shideleff.com>
Cc: sid@sources.redhat.com
Subject: Re: Level sensitive ARM interrupts
Date: Wed, 04 Aug 2004 15:43:00 -0000 [thread overview]
Message-ID: <20040804154259.GF20999@redhat.com> (raw)
In-Reply-To: <200408041117.50677.bigbob@shideleff.com>
[-- Attachment #1: Type: text/plain, Size: 374 bytes --]
Hi, Robert -
On Wed, Aug 04, 2004 at 11:17:45AM -0400, Robert Shideleff wrote:
> Oh yeah. Sorry, but I've been pretty busy lately. I've got all of the
> approvals and here is the updated patch.
>
> By the way, I've found SID to be extremely useful, even after hardware is
> available.
> [...]
Thank you very much; your patch is committed to CVS.
- FChE
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-08-04 15:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-02 18:37 Robert Shideleff
2004-07-02 18:39 ` Robert Shideleff
2004-07-05 0:27 ` Ben Elliston
[not found] ` <200407141850.05451.bigbob@shideleff.com>
[not found] ` <20040804023021.GA16871@redhat.com>
[not found] ` <200408041117.50677.bigbob@shideleff.com>
2004-08-04 15:43 ` Frank Ch. Eigler [this message]
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=20040804154259.GF20999@redhat.com \
--to=fche@redhat.com \
--cc=bigbob@shideleff.com \
--cc=sid@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).