From: gregkh@linuxfoundation.org (Greg KH)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 7/10] iio: lpc32xx-adc: Remove driver conflict due to device tree
Date: Wed, 18 Apr 2012 15:02:26 -0700 [thread overview]
Message-ID: <20120418220226.GA8035@kroah.com> (raw)
In-Reply-To: <1334756176-25144-8-git-send-email-stigge@antcom.de>
On Wed, Apr 18, 2012 at 03:36:12PM +0200, Roland Stigge wrote:
> Previously, the touchscreen and ADC drivers of the LPC32xx SoC had a Kconfig
> conflict declared because they use the same hardware. Upon the introduction of
> device tree support in both drivers, the conflict must be removed to enable
> the same kernel to support different hardware (configured via the device tree).
>
> Signed-off-by: Roland Stigge <stigge@antcom.de>
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
next prev parent reply other threads:[~2012-04-18 22:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 13:36 [PATCH v3 0/10] Second patchset for LPC32xx device tree conversion Roland Stigge
2012-04-18 13:36 ` [PATCH v3 1/10] ohci-nxp: Driver cleanup Roland Stigge
2012-04-18 13:36 ` [PATCH v3 2/10] ohci-nxp: Device tree support Roland Stigge
2012-04-18 13:36 ` [PATCH v3 3/10] ARM: LPC32xx: clock.c cleanup Roland Stigge
2012-04-18 13:36 ` [PATCH v3 4/10] ARM: LPC32xx: clock.c dma adjustment Roland Stigge
2012-04-18 13:36 ` [PATCH v3 5/10] ARM: LPC32xx: Remove obsolete platform Kconfig Roland Stigge
2012-04-18 13:36 ` [PATCH v3 6/10] input: Device tree support for LPC32xx touchscreen Roland Stigge
2012-04-18 13:36 ` [PATCH v3 7/10] iio: lpc32xx-adc: Remove driver conflict due to device tree Roland Stigge
2012-04-18 22:02 ` Greg KH [this message]
2012-04-18 13:36 ` [PATCH v3 8/10] ARM: LPC32xx: DTS files for device tree conversion Roland Stigge
2012-04-18 13:36 ` [PATCH v3 9/10] ARM: LPC32xx: Device tree support Roland Stigge
2012-04-18 13:36 ` [PATCH v3 10/10] ARM: LPC32xx: Move common code to common.c Roland Stigge
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=20120418220226.GA8035@kroah.com \
--to=gregkh@linuxfoundation.org \
--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;
as well as URLs for NNTP newsgroup(s).