From: Oskar Senft <osk-lkml@sirrix.de>
To: Greg KH <greg@kroah.com>
Cc: Aleksey Gorelov <Aleksey_Gorelov@Phoenix.com>,
linux-kernel@vger.kernel.org
Subject: Re: USB host pci-quirks
Date: Fri, 27 Jan 2006 09:12:51 +0100 [thread overview]
Message-ID: <43D9D603.4030909@sirrix.de> (raw)
In-Reply-To: <20060127004746.GA17030@kroah.com>
Dear Greg, dear Aleksey,
thank you for your response!
> A major distro has shipped for a while with this always enabled with no
> problems, which has helped with this.
I see, ok!
I think we'll find some workaround in our virtualization environment,
but now I know how it came to the current situation.
Thank you,
Oskar.
next prev parent reply other threads:[~2006-01-27 8:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-26 22:17 USB host pci-quirks Aleksey Gorelov
2006-01-26 22:38 ` Oskar Senft
2006-01-27 0:47 ` Greg KH
2006-01-27 8:12 ` Oskar Senft [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-26 23:16 Aleksey Gorelov
2006-01-26 11:03 Oskar Senft
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=43D9D603.4030909@sirrix.de \
--to=osk-lkml@sirrix.de \
--cc=Aleksey_Gorelov@Phoenix.com \
--cc=greg@kroah.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;
as well as URLs for NNTP newsgroup(s).