linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: David Miller <davem@davemloft.net>
Cc: "anemo@mba.ocn.ne.jp" <anemo@mba.ocn.ne.jp>,
	"Sosnowski, Maciej" <maciej.sosnowski@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH] net_dma: call dmaengine_get only if NET_DMA enabled
Date: Fri, 06 Feb 2009 23:03:11 -0700	[thread overview]
Message-ID: <498D241F.4080005@intel.com> (raw)
In-Reply-To: <20090206.215533.166740686.davem@davemloft.net>

David Miller wrote:
> From: David Miller <davem@davemloft.net>
> Date: Fri, 06 Feb 2009 19:29:10 -0800 (PST)
> 
>> From: Dan Williams <dan.j.williams@intel.com>
>> Date: Fri, 6 Feb 2009 15:52:35 -0700
>>
>>> Yes, it has been on the todo list for a while, but I eventually want
>>> the net case to look more like the raid case.  I.e. have one code path
>>> that picks async versus sync at runtime, with the option to compile
>>> out async support with header file ifdefs only.
>> And how does any of that get us any closer to a fix right now
>> for this problem that doesn't require an ifdef?
>>
>> Someone please work on this.
> 
> I guess that'd end up being me....

Not necessarily, you did snap me back into reality with that comment.

> 
> How about something like this?

Looks good.

Thanks,
Dan


  reply	other threads:[~2009-02-07  6:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-06 16:02 [PATCH] net_dma: call dmaengine_get only if NET_DMA enabled Atsushi Nemoto
2009-02-06 21:15 ` Dan Williams
2009-02-06 22:09   ` David Miller
2009-02-06 22:52     ` Dan Williams
2009-02-07  3:29       ` David Miller
2009-02-07  5:55         ` David Miller
2009-02-07  6:03           ` Dan Williams [this message]
2009-02-07  6:05             ` 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=498D241F.4080005@intel.com \
    --to=dan.j.williams@intel.com \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maciej.sosnowski@intel.com \
    --cc=netdev@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).