From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/2] i2c: sunxi: Change i2c compatibles
Date: Fri, 14 Mar 2014 10:13:53 +0100 [thread overview]
Message-ID: <20140314091353.GK2815@lukather> (raw)
In-Reply-To: <20140313173128.GC25870@e106331-lin.cambridge.arm.com>
On Thu, Mar 13, 2014 at 05:31:28PM +0000, Mark Rutland wrote:
> On Thu, Mar 13, 2014 at 11:37:22AM +0000, Maxime Ripard wrote:
> > The Allwinner A10 compatibles were following a slightly different compatible
> > patterns than the rest of the SoCs for historical reasons. Move to the other
> > pattern for consistency across all Allwinner Socs.
>
> Dropping support for the existing string breaks existing DTBs. Is
> this really necessary?
I added new ones at first, and Rob said it wasn't worth it since we
were a "work-in-progress" platform.
http://lists.infradead.org/pipermail/linux-arm-kernel/2014-February/229438.html
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- 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/20140314/8d5d4eb4/attachment.sig>
next prev parent reply other threads:[~2014-03-14 9:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 11:37 [PATCH v3 0/2] i2c: sunxi: Change compatibles pattern Maxime Ripard
2014-03-13 11:37 ` [PATCH v3 1/2] i2c: sunxi: Change i2c compatibles Maxime Ripard
2014-03-13 17:31 ` Mark Rutland
2014-03-14 9:13 ` Maxime Ripard [this message]
2014-03-13 11:37 ` [PATCH v3 2/2] ARM: sunxi: dt: Convert to the new " Maxime Ripard
2014-03-13 21:27 ` Wolfram Sang
2014-03-24 14:39 ` Maxime Ripard
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=20140314091353.GK2815@lukather \
--to=maxime.ripard@free-electrons.com \
--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).