mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: David Miller <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	torvalds@linux-foundation.org
Subject: Re: [ATA]: Don't allow to enable this for SPARC64 without PCI.
Date: Mon, 4 Jun 2007 17:58:41 -0400	[thread overview]
Message-ID: <20070604215841.GK20299@havoc.gtf.org> (raw)
In-Reply-To: <20070604.142736.27799798.davem@davemloft.net>

On Mon, Jun 04, 2007 at 02:27:36PM -0700, David Miller wrote:
> From: Jeff Garzik <jeff@garzik.org>
> Date: Mon, 4 Jun 2007 17:09:52 -0400
> 
> > Um, this was NAK'd:
> > 
> > libata uses generic DMA and generic struct device.  Neither of which
> > are specific to SPARC64 or PCI.
> > 
> > Did you read the code?
> > Did you read the thread on which you were CC'd?
> > Did you see the NAKs from me and Alan (and others)?
> 
> It went in before any of you replied, to be fair.

Sounds like we should taunt Linus for being slow then ;) ;)


> I'm willing to fix this in other ways, but there is simply
> no hardware that's going to work in that kind of configuration
> (non-PCI) on sparc64 so building it in that state is going to
> be purely for the purposes of intellectual curiosity :-)

Should be easy enough to add dma_xxx wrappers that do nothing but
return an error.

As long as this change is _temporary_, I'm happy.

As you saw from my reply, apply a driver fix for a platform problem
makes me twitch in a big way... :)

	Jeff




  reply	other threads:[~2007-06-04 21:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200706042059.l54Kx6jR031700@hera.kernel.org>
2007-06-04 21:09 ` Jeff Garzik
2007-06-04 21:27   ` David Miller
2007-06-04 21:58     ` Jeff Garzik [this message]
2007-06-04 22:03       ` 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=20070604215841.GK20299@havoc.gtf.org \
    --to=jeff@garzik.org \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®