From: Jesse Barnes <jesse.barnes@intel.com>
To: "Jan Beulich" <jbeulich@novell.com>
Cc: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
davem@redhat.com
Subject: Re: PCI DAC DMA APIs
Date: Thu, 15 Mar 2007 11:37:44 -0700 [thread overview]
Message-ID: <200703151137.44538.jesse.barnes@intel.com> (raw)
In-Reply-To: <45F94C45.76E4.0078.0@novell.com>
On Thursday, March 15, 2007 5:38 am Jan Beulich wrote:
> While the kernel headers provide for this, there don't appear to be
> any in-tree users (which seems contrary to general Linux policies).
> Would there be objections to remove all of these?
It should be safe to kill them, but I remember arguing with davem about
this stuff in the past...
Jesse
next prev parent reply other threads:[~2007-03-15 18:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-15 12:38 PCI DAC DMA APIs Jan Beulich
2007-03-15 13:23 ` Andi Kleen
2007-03-15 18:37 ` Jesse Barnes [this message]
2007-03-15 19:18 ` Christoph Hellwig
2007-03-16 1:18 ` David Miller
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=200703151137.44538.jesse.barnes@intel.com \
--to=jesse.barnes@intel.com \
--cc=davem@redhat.com \
--cc=jbeulich@novell.com \
--cc=linux-arch@vger.kernel.org \
--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