From: Arnd Bergmann <arnd@arndb.de>
To: "Jean-Christophe PLAGNIOL-VILLARD" <plagnioj@jcrosoft.com>
Cc: Alan Ott <alan@signal11.us>, Andrew Victor <linux@maxim.org.za>,
Nicolas Ferre <nicolas.ferre@atmel.com>,
Russell King <linux@arm.linux.org.uk>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Ben Dooks <ben-linux@fluff.org>
Subject: Re: [PATCH v2 1/2] ARM: AT91: Add parameter for AT91_HAS_PATA
Date: Sun, 11 Mar 2012 21:36:47 +0000 [thread overview]
Message-ID: <201203112136.47694.arnd@arndb.de> (raw)
In-Reply-To: <20120311183856.GA13869@game.jcrosoft.org>
On Sunday 11 March 2012, Jean-Christophe PLAGNIOL-VILLARD wrote:
> >
> > diff --git a/arch/arm/mach-at91/Kconfig b/arch/arm/mach-at91/Kconfig
> > index 71feb00..9eeeabe 100644
> > --- a/arch/arm/mach-at91/Kconfig
> > +++ b/arch/arm/mach-at91/Kconfig
> > @@ -24,6 +24,9 @@ config AT91_SAM9_ALT_RESET
> > config AT91_SAM9G45_RESET
> > bool
> >
> > +config AT91_HAS_PATA
> > + bool
> what is the need for this?
>
> As we switch to DT, I don't want to track the soc list in the Kconfig anymore
> if the soc support the PATA will be describe in the DT
>
When I originally wrote the patch, I was hitting build errors when trying
to enable the at91 pata driver on socs that don't have the right declarations
in their headers. If that has been resolved in a better way already, this
patch can be dropped.
Arnd
next prev parent reply other threads:[~2012-03-11 21:37 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 [this message]
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
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=201203112136.47694.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=alan@signal11.us \
--cc=ben-linux@fluff.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=linux@maxim.org.za \
--cc=nicolas.ferre@atmel.com \
--cc=plagnioj@jcrosoft.com \
/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