From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Jens Axboe <axboe@suse.de>, Jeff Garzik <jgarzik@pobox.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: SMP+irq handling broken in current git?
Date: Fri, 24 Jun 2005 00:26:37 +0100 [thread overview]
Message-ID: <1119569195.18655.63.camel@localhost.localdomain> (raw)
In-Reply-To: <200506231258.35258.bjorn.helgaas@hp.com>
On Iau, 2005-06-23 at 19:58, Bjorn Helgaas wrote:
> Do you have any VIA devices? If so, you might try the attached.
> (Just for debugging; if the patch helps, I have no idea how to
> do it correctly.)
The VIA routing is documented in the bridge chipset docs. The older ones
are/were on the ftp site. The newer ones are available under NDA or by
asking nicely and having a reason.
next prev parent reply other threads:[~2005-06-23 23:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-23 13:53 SMP+irq handling broken in current git? Jens Axboe
2005-06-23 16:59 ` Jeff Garzik
2005-06-23 18:42 ` Jens Axboe
2005-06-23 18:58 ` Bjorn Helgaas
2005-06-23 19:11 ` Jens Axboe
2005-06-23 19:20 ` Bjorn Helgaas
2005-06-23 23:26 ` Alan Cox [this message]
2005-06-24 10:12 ` Jens Axboe
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=1119569195.18655.63.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=axboe@suse.de \
--cc=bjorn.helgaas@hp.com \
--cc=jgarzik@pobox.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