linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Greg KH <gregkh@suse.de>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH -next] staging/phison: fix kconfig for clean build
Date: Mon, 16 Feb 2009 08:46:16 -0800	[thread overview]
Message-ID: <49999858.6000604@oracle.com> (raw)
In-Reply-To: <20090216172016.f1d159a7.sfr@canb.auug.org.au>

From: Randy Dunlap <randy.dunlap@oracle.com>

phison is an ATA driver, not a classic IDE driver, so fix the Kconfig file
so that it will build.

drivers/staging/phison/phison.c:43: error: implicit declaration of function 'ATA_BMDMA_SHT'
drivers/staging/phison/phison.c:43: error: initializer element is not constant
drivers/staging/phison/phison.c:43: error: (near initialization for 'phison_sht.module')
drivers/staging/phison/phison.c:47: error: 'ata_bmdma_port_ops' undeclared here (not in a function)
drivers/staging/phison/phison.c:65: error: implicit declaration of function 'ata_pci_sff_init_one'

Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
 drivers/staging/phison/Kconfig |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- linux-next-20090216.orig/drivers/staging/phison/Kconfig
+++ linux-next-20090216/drivers/staging/phison/Kconfig
@@ -1,5 +1,5 @@
 config IDE_PHISON
 	tristate "PCIE ATA PS5000 IDE support"
-	depends on IDE
+	depends on ATA && ATA_SFF
 	---help---
 	  This is an experimental driver for PS5000 IDE driver.

  parent reply	other threads:[~2009-02-16 16:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-16  6:20 linux-next: Tree for February 16 Stephen Rothwell
2009-02-16  8:54 ` next Feb 16 build break [usb/host/fhci-*] Sachin P. Sant
     [not found]   ` <499929CB.2030004-xthvdsQ13ZrQT0dZR+AlfA@public.gmane.org>
2009-02-16 10:13     ` Stephen Rothwell
2009-02-16 13:40       ` [Patch - Next] [USB/FHCI] use dev_name() in place of bus_id Sachin P. Sant
     [not found]         ` <49996CBB.7040007-xthvdsQ13ZrQT0dZR+AlfA@public.gmane.org>
2009-02-16 13:48           ` Anton Vorontsov
2009-02-16 16:46 ` Randy Dunlap [this message]
2009-02-17  0:55 ` next-20090216: slqb Alexey Dobriyan
2009-02-17 10:27   ` Nick Piggin
2009-02-17 11:31     ` Pekka Enberg
2009-02-17 12:48       ` Peter Zijlstra
2009-02-17  9:55 ` linux-next: USB mouse won't work after resume Laurent Riffard
2009-02-17 10:35   ` Oliver Neukum
     [not found]     ` <200902171135.13329.oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>
2009-02-17 13:37       ` Laurent Riffard
2009-02-17 15:12         ` Alan Stern
2009-02-17 20:42         ` Oliver Neukum
2009-02-17 21:05           ` Alan Stern
2009-02-18  9:51             ` Jiri Slaby
2009-02-18  0:31           ` Laurent Riffard
2009-02-18  8:47             ` Oliver Neukum
     [not found]           ` <200902172142.57302.oliver-GvhC2dPhHPQdnm+yROfE0A@public.gmane.org>
2009-02-18 16:51             ` Alan Stern
2009-02-18 17:06               ` Oliver Neukum

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=49999858.6000604@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).