From: Andi Kleen <ak@suse.de>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: David Brownell <david-b@pacbell.net>,
yinghai.lu@amd.com, stuge-linuxbios@cdy.org,
stepan@coresystems.de, linuxbios@linuxbios.org,
linux-usb-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, gregkh@suse.de
Subject: Re: [linux-usb-devel] [RFC][PATCH 0/2] x86_64 Early usb debug port support.
Date: Wed, 6 Dec 2006 22:59:45 +0100 [thread overview]
Message-ID: <200612062259.46140.ak@suse.de> (raw)
In-Reply-To: <m1y7pk4sfa.fsf@ebiederm.dsl.xmission.com>
> > However I suppose it would be ok to switch Eric's code between early
> > pci access and locked one once the PCI subsystem is up and running.
> > Just don't forget bust_spinlocks()
>
> No pci access on that path.
Hmm good point. Ok ignore that then.
keep should be default then.
-Andi
next prev parent reply other threads:[~2006-12-06 22:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 20:43 [linux-usb-devel] [RFC][PATCH 0/2] x86_64 Early usb debug port support Lu, Yinghai
2006-12-06 20:58 ` Andi Kleen
2006-12-06 21:12 ` Eric W. Biederman
2006-12-06 21:17 ` David Brownell
2006-12-06 21:24 ` Andi Kleen
2006-12-06 21:37 ` Eric W. Biederman
2006-12-06 21:59 ` Andi Kleen [this message]
2006-12-06 23:47 ` David Brownell
-- strict thread matches above, loose matches on Subject: below --
2006-12-06 21:08 Lu, Yinghai
2006-12-01 18:55 [LinuxBIOS] #57: libusb host program for PLX NET20DC debug device Lu, Yinghai
2006-12-03 15:49 ` Eric W. Biederman
2006-12-04 5:09 ` [RFC][PATCH 0/2] x86_64 Early usb debug port support Eric W. Biederman
[not found] ` <200612042001.09808.david-b@pacbell.net>
2006-12-05 11:01 ` [linux-usb-devel] " Eric W. Biederman
2006-12-06 17:31 ` Andi Kleen
2006-12-05 11:18 ` 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=200612062259.46140.ak@suse.de \
--to=ak@suse.de \
--cc=david-b@pacbell.net \
--cc=ebiederm@xmission.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=linuxbios@linuxbios.org \
--cc=stepan@coresystems.de \
--cc=stuge-linuxbios@cdy.org \
--cc=yinghai.lu@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.