From: Dave Jones <davej@redhat.com>
To: "Rafał Bilski" <rafalbilski@interia.pl>
Cc: Dave Jones <davej@codemonkey.org.uk>, cpufreq@lists.linux.org.uk
Subject: Re: Longhaul - infrastructure(?) proposal
Date: Thu, 29 Jun 2006 15:28:09 -0400 [thread overview]
Message-ID: <20060629192809.GC2067@redhat.com> (raw)
In-Reply-To: <44A3EC2F.7040909@interia.pl>
On Thu, Jun 29, 2006 at 05:05:19PM +0200, Rafał Bilski wrote:
> Hello!
>
> In case that flushing and disabling caches will not work.
> It is possible that I do above in wrong way.
> Would this code below be acceptable as infrastructure?
> Is this infrastructure or maybe hack?
> This is draft/proposal.
> Can I continue in this way or I shouldn't?
I suggest to keep talking with Greg, as any work on quiescing dma will
need cooperation from both USB & PCI layers, and he's one of the
more knowledgable people in the area of the driver model.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-06-29 19:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-29 15:05 Longhaul - infrastructure(?) proposal Rafał Bilski
2006-06-29 19:28 ` Dave Jones [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-29 20:26 Rafał Bilski
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=20060629192809.GC2067@redhat.com \
--to=davej@redhat.com \
--cc=cpufreq@lists.linux.org.uk \
--cc=davej@codemonkey.org.uk \
--cc=rafalbilski@interia.pl \
/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.