From: wsa@the-dreams.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/5] Add-Broadcom-Kona-I2C-Support
Date: Fri, 15 Nov 2013 23:52:34 +0100 [thread overview]
Message-ID: <20131115225234.GC2672@katana> (raw)
In-Reply-To: <1384462936-7906-1-git-send-email-tim.kryger@linaro.org>
On Thu, Nov 14, 2013 at 01:02:11PM -0800, Tim Kryger wrote:
> This series adds support for the Kona I2C bus found on Broadcom mobile
> SoCs like the bcm11351 (aka bcm281xx) and enables it on the bcm28155-ap
> board.
>
> It depends upon the following commit:
> http://lkml.indiana.edu/hypermail/linux/kernel/1311.1/03583.html
Fixed Kconfig sorting, squashed broken out patches 1-3 into one and
applied to for-next, thanks! Let me know if I should take patches 4-5
also, but usually they go via arm-soc. Also, please provide a "Changes
since V1" log which will speed up reviewing.
Thanks,
Wolfram
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20131115/9aa11b15/attachment.sig>
next prev parent reply other threads:[~2013-11-15 22:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 21:02 [PATCH v2 0/5] Add-Broadcom-Kona-I2C-Support Tim Kryger
2013-11-14 21:02 ` [PATCH v2 1/5] Documentation: dt: Add i2c-bcm-kona binding Tim Kryger
2013-11-14 21:02 ` [PATCH v2 2/5] i2c: i2c-bcm-kona: Introduce Broadcom I2C Driver Tim Kryger
2013-11-14 21:02 ` [PATCH v2 3/5] i2c: i2c-bcm-kona: Add support for high-speed mode Tim Kryger
2013-11-14 21:02 ` [PATCH v2 4/5] ARM: dts: bcm281xx: Add i2c busses Tim Kryger
2013-11-14 21:02 ` [PATCH v2 5/5] ARM: dts: bcm28155-ap: Enable all the " Tim Kryger
2013-11-15 22:52 ` Wolfram Sang [this message]
2013-11-15 23:30 ` [PATCH v2 0/5] Add-Broadcom-Kona-I2C-Support Tim Kryger
2013-11-18 16:12 ` Christian Daudt
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=20131115225234.GC2672@katana \
--to=wsa@the-dreams.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).