From: Andi Kleen <ak@suse.de>
To: ebiederm@xmission.com (Eric W. Biederman)
Cc: Dave Olson <olson@unixfolk.com>, <linux-kernel@vger.kernel.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
discuss@x86-64.org
Subject: Re: [PATCH 2/2] Initial generic hypertransport interrupt support.
Date: 12 Jul 2006 00:27:54 +0200 [thread overview]
Message-ID: <p734pxnojyt.fsf@verdi.suse.de> (raw)
In-Reply-To: <m1bqrxm6zm.fsf@ebiederm.dsl.xmission.com>
ebiederm@xmission.com (Eric W. Biederman) writes:
> This patch implements two functions ht_create_irq and ht_destroy_irq
> for use by drivers. Several other functions are implemented as helpers
> for arch specific irq_chip handlers.
What do you want to use it for? Normally all HT configuration should be handled
by the BIOS and not messed with by the kernel.
-Andi
next prev parent reply other threads:[~2006-07-11 22:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-10 22:14 [PATCH 1/2] Add Hypertransport capability defines Eric W. Biederman
2006-07-10 22:26 ` [PATCH 2/2] Initial generic hypertransport interrupt support Eric W. Biederman
2006-07-10 22:39 ` Benjamin Herrenschmidt
2006-07-11 3:51 ` Eric W. Biederman
2006-07-11 5:20 ` Benjamin Herrenschmidt
2006-07-11 6:29 ` Eric W. Biederman
2006-07-11 7:29 ` Segher Boessenkool
2006-07-11 7:48 ` Eric W. Biederman
2006-07-11 9:15 ` Benjamin Herrenschmidt
2006-07-11 19:56 ` Eric W. Biederman
2006-07-11 22:18 ` Benjamin Herrenschmidt
2006-07-11 22:27 ` Andi Kleen [this message]
2006-07-12 3:05 ` Eric W. Biederman
2006-07-12 6:10 ` Dave Olson
2006-07-12 6:56 ` Eric W. Biederman
2006-07-13 3:56 ` Dave Olson
2006-07-13 15:13 ` Eric W. Biederman
2006-07-13 18:15 ` Dave Olson
2006-07-13 18:41 ` Eric W. Biederman
2006-07-13 19:00 ` Dave Olson
2006-07-13 19:20 ` Eric W. Biederman
2006-07-13 19:34 ` Dave Olson
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=p734pxnojyt.fsf@verdi.suse.de \
--to=ak@suse.de \
--cc=benh@kernel.crashing.org \
--cc=discuss@x86-64.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olson@unixfolk.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