public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: greg@kroah.com
Cc: netdev@vger.kernel.org
Subject: Re: Network drivers with direct io memory accesses
Date: Wed, 14 May 2008 17:13:15 -0700 (PDT)	[thread overview]
Message-ID: <20080514.171315.87012656.davem@davemloft.net> (raw)
In-Reply-To: <20080515001044.GA2772@kroah.com>

From: Greg KH <greg@kroah.com>
Date: Wed, 14 May 2008 17:10:44 -0700

> Both of these drivers are accessing memory on the devices directly,
> without using the proper kernel abstractions for it, making them usable
> only on x86-based boxes probably.
> 
> My question is, does this have to be fixed in order to get them
> accepted into the tree?

I'd say yes.

If that aspect isn't fixed I can't even build test them on my
computers.

  reply	other threads:[~2008-05-15  0:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-15  0:10 Network drivers with direct io memory accesses Greg KH
2008-05-15  0:13 ` David Miller [this message]
2008-05-15  0:28   ` Greg KH
2008-05-20 18:33     ` Greg KH

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=20080514.171315.87012656.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=greg@kroah.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