From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Peter Griffin <peter.griffin@linaro.org>
Cc: linux-kernel@vger.kernel.org, linaro-kernel@lists.linaro.org,
Arnd Bergmann <arnd@arndb.de>,
Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
linux-fbdev@vger.kernel.org, Anatolij Gustschin <agust@denx.de>
Subject: Re: [PATCH 03/13] video: clarify I2C dependencies
Date: Thu, 24 Apr 2014 12:32:35 +0000 [thread overview]
Message-ID: <20140424123235.GS26756@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1398342509-10243-4-git-send-email-peter.griffin@linaro.org>
On Thu, Apr 24, 2014 at 01:28:19PM +0100, Peter Griffin wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> We can only use I2C support in frame buffer drivers if
> Either I2C is built-in, or both I2C and the driver itself
> are loadable modules.
Why?
--
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.
next prev parent reply other threads:[~2014-04-24 12:32 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1398342509-10243-1-git-send-email-peter.griffin@linaro.org>
2014-04-24 12:28 ` [PATCH 01/13] video: sh_mobile_lcdcfb depends on meram Peter Griffin
2014-04-24 12:28 ` [PATCH 02/13] video: omap2dss: fix LPAE warnings Peter Griffin
2014-04-24 12:28 ` [PATCH 03/13] video: clarify I2C dependencies Peter Griffin
2014-04-24 12:32 ` Russell King - ARM Linux [this message]
2014-04-24 12:48 ` Arnd Bergmann
2014-04-24 12:28 ` [PATCH 04/13] video/omap: fix modular build Peter Griffin
2014-04-24 12:28 ` [PATCH 05/13] video/mbx: fix building debugfs support Peter Griffin
2014-04-24 12:28 ` [PATCH 06/13] video: export fb_prepare_logo Peter Griffin
2014-04-24 12:28 ` [PATCH 07/13] video: atmel needs FB_BACKLIGHT Peter Griffin
2014-04-24 12:28 ` [PATCH 08/13] video/backlight: LM3630A needs PWM Peter Griffin
2014-04-24 16:45 ` Bryan Wu
2014-04-25 9:00 ` Jingoo Han
2014-04-28 10:14 ` Lee Jones
2014-04-24 12:28 ` [PATCH 09/13] video/backlight: LP8788 " Peter Griffin
2014-04-24 16:45 ` Bryan Wu
2014-04-24 22:42 ` Milo Kim
2014-04-25 8:54 ` Jingoo Han
2014-04-28 10:16 ` Lee Jones
2014-04-24 12:28 ` [PATCH 10/13] video/pxa: LCD_CORGI needs BACKLIGHT_CLASS_DEVICE Peter Griffin
2014-04-24 16:46 ` Bryan Wu
2014-04-25 8:58 ` Jingoo Han
2014-04-28 10:15 ` Lee Jones
2014-04-24 12:28 ` [PATCH 11/13] video/nuc900: allow modular build Peter Griffin
2014-04-24 12:28 ` [PATCH 12/13] video/backlight: LP855X needs PWM Peter Griffin
2014-04-24 16:48 ` Bryan Wu
2014-04-24 22:43 ` Milo Kim
2014-04-25 9:02 ` Jingoo Han
2014-04-28 10:16 ` Lee Jones
2014-04-24 12:28 ` [PATCH 13/13] video: omap: allow building on !MMU Peter Griffin
2014-05-07 9:14 ` Tomi Valkeinen
2014-05-08 21:53 ` Tony Lindgren
2014-05-08 23:04 ` Aaro Koskinen
2014-05-08 23:17 ` Tony Lindgren
2014-05-09 21:21 ` Aaro Koskinen
2014-05-11 15:01 ` Tony Lindgren
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=20140424123235.GS26756@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=agust@denx.de \
--cc=arnd@arndb.de \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.griffin@linaro.org \
--cc=plagnioj@jcrosoft.com \
--cc=tomi.valkeinen@ti.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;
as well as URLs for NNTP newsgroup(s).