From: balbi@ti.com (Felipe Balbi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] AT91: add AT91SAM9X5 dummy configuration variable
Date: Tue, 28 Jun 2011 13:35:50 +0300 [thread overview]
Message-ID: <20110628103549.GG2612@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <1309260927-11411-1-git-send-email-nicolas.ferre@atmel.com>
On Tue, Jun 28, 2011 at 01:35:27PM +0200, Nicolas Ferre wrote:
> Add this Kconfig variable to ease the submission of this chip support.
> As this chip/board inclusion is dealayed due to deep consolidation of
> arm/mach-at91 sources, we include this dummy configuration variable to allow
> submission of SAM9x5 related drivers in other subsystems.
Why are the drivers even depending on this ? They should be portable
enough. Can you share a few drivers so we have a look ?
IMHO, the whole idea of the consolidation is beyond arch/arm, drivers
should be affected too.
--
balbi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 490 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20110628/46dfaa3e/attachment.sig>
next prev parent reply other threads:[~2011-06-28 10:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-28 11:35 [PATCH] AT91: add AT91SAM9X5 dummy configuration variable Nicolas Ferre
2011-06-28 10:35 ` Felipe Balbi [this message]
2011-06-28 12:13 ` Nicolas Ferre
2011-06-28 12:26 ` Felipe Balbi
2011-06-28 16:02 ` Jean-Christophe PLAGNIOL-VILLARD
2011-06-29 9:30 ` Felipe Balbi
2011-06-29 15:24 ` Nicolas Ferre
2011-06-29 15:39 ` Felipe Balbi
2011-07-02 9:49 ` Arnd Bergmann
2011-07-04 9:23 ` Nicolas Ferre
2011-07-05 5:32 ` Jean-Christophe PLAGNIOL-VILLARD
2011-07-05 11:25 ` Arnd Bergmann
2011-06-28 16:03 ` Jean-Christophe PLAGNIOL-VILLARD
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=20110628103549.GG2612@legolas.emea.dhcp.ti.com \
--to=balbi@ti.com \
--cc=linux-arm-kernel@lists.infradead.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