From: Sergei Shtylyov <sshtylyov@mvista.com>
To: Alan Ott <alan@signal11.us>
Cc: Jeff Garzik <jgarzik@pobox.com>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>, Ben Dooks <ben-linux@fluff.org>
Subject: Re: [PATCH v2 2/2] ata: AT91 ata driver requires AT91_HAS_PATA
Date: Sun, 11 Mar 2012 14:10:37 +0400 [thread overview]
Message-ID: <4F5C7A1D.60208@mvista.com> (raw)
In-Reply-To: <1331415562-10994-1-git-send-email-alan@signal11.us>
Hello.
On 11-03-2012 1:39, Alan Ott wrote:
> This driver uses registers defined in a per-soc header file.
> Since not every soc in the at91 platform defines those, make
> the Kconfig option dependent on those which define
> AT91_HAS_PATA.
> This is based on a patch by Arnd Bergmann.
> Signed-off-by: Arnd Bergmann<arnd@arndb.de>
> Signed-off-by: Alan Ott<alan@signal11.us>
> CC: Ben Dooks<ben-linux@fluff.org>
> ---
> drivers/ata/Kconfig | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
> diff --git a/drivers/ata/Kconfig b/drivers/ata/Kconfig
> index 6bdedd7..fdb8c90 100644
> --- a/drivers/ata/Kconfig
> +++ b/drivers/ata/Kconfig
> @@ -731,6 +731,7 @@ config PATA_AT32
> config PATA_AT91
> tristate "PATA support for AT91SAM9260"
> depends on ARM && ARCH_AT91
Is this line still needed?
> + depends on AT91_HAS_PATA
> help
> This option enables support for IDE devices on the Atmel AT91SAM9260 SoC.
WBR, Sergei
next prev parent reply other threads:[~2012-03-11 10:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-10 18:53 [PATCH 0/1] ARM: AT91: drivers: cleanup patches from Arnd Bergmann Alan Ott
2012-03-10 18:54 ` [PATCH 1/1] ata: AT91 ata driver requires specific platforms Alan Ott
2012-03-10 19:56 ` Ben Dooks
2012-03-10 21:36 ` [PATCH v2 0/2] " Alan Ott
2012-03-10 21:38 ` [PATCH v2 1/2] ARM: AT91: Add parameter for AT91_HAS_PATA Alan Ott
2012-03-11 18:38 ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-11 21:36 ` Arnd Bergmann
2012-03-10 21:39 ` [PATCH v2 2/2] ata: AT91 ata driver requires AT91_HAS_PATA Alan Ott
2012-03-11 10:10 ` Sergei Shtylyov [this message]
2012-03-13 20:46 ` Jeff Garzik
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=4F5C7A1D.60208@mvista.com \
--to=sshtylyov@mvista.com \
--cc=alan@signal11.us \
--cc=arnd@arndb.de \
--cc=ben-linux@fluff.org \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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