All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: Network drivers with direct io memory accesses
Date: Tue, 20 May 2008 11:33:45 -0700	[thread overview]
Message-ID: <20080520183345.GA12937@kroah.com> (raw)
In-Reply-To: <20080515002824.GA3636@kroah.com>

On Wed, May 14, 2008 at 05:28:24PM -0700, Greg KH wrote:
> On Wed, May 14, 2008 at 05:13:15PM -0700, David Miller wrote:
> > 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.
> 
> {sigh}
> 
> I figured that, but thought it would be worth it to at least ask. :)
> 
> > If that aspect isn't fixed I can't even build test them on my
> > computers.
> 
> Hm, why?  They should still build I would think, just not run properly,
> right?
> 
> Damm, I really gotta get that cross-build system set up here, I'll go
> start that right now...

Ok, I did this, and I don't see any build errors or warnings on sparc64.
Maybe the code isn't as bad as I imagined, I'll go through it all and
submit it for review.

thanks,

greg k-h

      reply	other threads:[~2008-05-20 18:34 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
2008-05-15  0:28   ` Greg KH
2008-05-20 18:33     ` Greg KH [this message]

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