From mboxrd@z Thu Jan 1 00:00:00 1970 From: santosh.shilimkar@ti.com (Santosh Shilimkar) Date: Thu, 10 Apr 2014 13:37:15 -0400 Subject: [PATCH 3/5] gpio: omap: add a GPIO_OMAP option instead of using ARCH_OMAP In-Reply-To: <1396796297-13002-4-git-send-email-javier.martinez@collabora.co.uk> References: <1396796297-13002-1-git-send-email-javier.martinez@collabora.co.uk> <1396796297-13002-4-git-send-email-javier.martinez@collabora.co.uk> Message-ID: <5346D6CB.6070003@ti.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Sunday 06 April 2014 10:58 AM, Javier Martinez Canillas wrote: > The ARCH_OMAP config option was used to built the GPIO OMAP > driver but this is not consistent with the rest of the GPIO > drivers that have their own Kconfig option. > > Also, this make it harder to add dependencies or reverse > dependencies (i.e: select) since that would mean touching the > sub-arch config option. > > So is better to add a boolean Kconfig option for this driver > that defaults to true if ARCH_OMAP is enabled. > > Signed-off-by: Javier Martinez Canillas > --- Acked-by: Santosh Shilimkar