From: ebiederm@xmission.com (Eric W. Biederman)
To: "Bryan O'Sullivan" <bos@pathscale.com>
Cc: olson@pathscale.com, <linux-kernel@vger.kernel.org>
Subject: [RFC][PATCH 0/2] htirq: generalization
Date: Fri, 03 Nov 2006 13:40:42 -0700 [thread overview]
Message-ID: <m1irhww9f9.fsf_-_@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <454B8E19.90300@pathscale.com> (Bryan O'Sullivan's message of "Fri, 03 Nov 2006 10:44:41 -0800")
Ok. I think this is what we need to do to generalize the
htirq code so that we can use it on hardware that doesn't
connect the standard configuration registers to control
of the htirq.
Bryan please take a look and see if you can use these to
fix the ipath hypertransport card driver.
Eric
next parent reply other threads:[~2006-11-03 20:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <454A7B0F.7060701@pathscale.com>
[not found] ` <m1odrpymqc.fsf@ebiederm.dsl.xmission.com>
[not found] ` <454B7B70.9060104@pathscale.com>
[not found] ` <m1d584xutk.fsf@ebiederm.dsl.xmission.com>
[not found] ` <454B880A.1010802@pathscale.com>
[not found] ` <m1zmb8wexd.fsf@ebiederm.dsl.xmission.com>
[not found] ` <454B8E19.90300@pathscale.com>
2006-11-03 20:40 ` Eric W. Biederman [this message]
2006-11-03 20:43 ` [PATCH 1/2] htirq: Refactor so we only have one function that writes to the chip Eric W. Biederman
2006-11-03 20:49 ` Bryan O'Sullivan
2006-11-03 21:46 ` [RFC][PATCH 2/2] htirq: Allow buggy drivers of buggy hardware to write the registers Eric W. Biederman
2006-11-04 19:37 ` Yinghai Lu
2006-11-04 19:45 ` Eric W. Biederman
2006-11-04 20:00 ` Yinghai Lu
2006-11-04 21:21 ` Eric W. Biederman
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=m1irhww9f9.fsf_-_@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=bos@pathscale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olson@pathscale.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
all inboxes | Powered by JetHome®