From: Paul Mundt <lethal@linux-sh.org>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 4/5] video: mb862xx: add support for controller's I2C bus adapter
Date: Tue, 24 May 2011 07:23:44 +0000 [thread overview]
Message-ID: <20110524072344.GF11986@linux-sh.org> (raw)
In-Reply-To: <1305302089-7666-5-git-send-email-agust@denx.de>
On Fri, May 13, 2011 at 05:54:48PM +0200, Anatolij Gustschin wrote:
> Add adapter driver for I2C adapter in Coral-P(A)/Lime GDCs.
> So we can easily access devices on controller's I2C bus using
> i2c-dev interface.
>
> Signed-off-by: Anatolij Gustschin <agust@denx.de>
I don't see anything in the Kconfig that prevents this from being built
with CONFIG_I2C=n, have you tested this case?
next prev parent reply other threads:[~2011-05-24 7:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 15:54 [PATCH 4/5] video: mb862xx: add support for controller's I2C bus adapter Anatolij Gustschin
2011-05-24 7:23 ` Paul Mundt [this message]
2011-05-24 7:45 ` [PATCH 4/5] video: mb862xx: add support for controller's I2C Anatolij Gustschin
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=20110524072344.GF11986@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-fbdev@vger.kernel.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).