From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] i2c: new bus driver for efm32
Date: Mon, 3 Mar 2014 12:20:05 +0100 [thread overview]
Message-ID: <20140303112005.GC17249@pengutronix.de> (raw)
In-Reply-To: <1392027598-29015-1-git-send-email-u.kleine-koenig@pengutronix.de>
On Mon, Feb 10, 2014 at 11:19:58AM +0100, Uwe Kleine-K?nig wrote:
> This was tested on a EFM32GG-DK3750 devboard that has a temperature
> sensor and an eeprom on its i2c bus.
>
> Signed-off-by: Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de>
still no reply :-(
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2014-03-03 11:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 10:19 [RFC PATCH] i2c: new bus driver for efm32 Uwe Kleine-König
2014-02-17 8:27 ` Uwe Kleine-König
2014-03-03 11:20 ` Uwe Kleine-König [this message]
2014-03-10 7:55 ` Wolfram Sang
2014-03-13 21:26 ` Uwe Kleine-König
2014-03-13 22:14 ` Wolfram Sang
2014-03-13 23:19 ` Uwe Kleine-König
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=20140303112005.GC17249@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--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).