From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/5] ARM: mvebu: Add i2c alias so setting bus number
Date: Mon, 24 Feb 2014 22:32:20 +0100 [thread overview]
Message-ID: <201402242232.20851.arnd@arndb.de> (raw)
In-Reply-To: <20140224193050.GG1010@titan.lakedaemon.net>
On Monday 24 February 2014, Jason Cooper wrote:
>
> ex: What changed from v3.15 to v3.16 for kirkwood?
>
> $ git log --oneline v3.15..v3.16 -- arch/arm/mach-mvebu | \
> grep -i 'ARM: kirkwood'
>
> This seems to be new territory for us (mvebu), perhaps one of the
> arm-soc maintainers has a preference? I'll add them to this reply.
I don't care, as long as you decide on something that works for you.
While you're transitioning, it probably makes little sense to
enforce either one too strictly.
Arnd
next prev parent reply other threads:[~2014-02-24 21:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 18:01 [PATCH v2 0/5] mvebu support for kirkwood HP T5325 Andrew Lunn
2014-02-24 18:01 ` [PATCH v2 1/5] ARM: Kirkwood: Add audio node to kirkwood.dtsi Andrew Lunn
2014-02-24 19:03 ` Jason Cooper
2014-02-24 18:01 ` [PATCH v2 2/5] ARM: mvebu: Add i2c alias so setting bus number Andrew Lunn
2014-02-24 19:05 ` Jason Cooper
2014-02-24 19:11 ` Andrew Lunn
2014-02-24 19:30 ` Jason Cooper
2014-02-24 21:32 ` Arnd Bergmann [this message]
2014-02-24 22:15 ` Jason Cooper
2014-02-24 18:01 ` [PATCH v2 3/5] ARM: mvebu: Add HP T5325 thin client Andrew Lunn
2014-02-24 19:10 ` Jason Cooper
2014-02-24 19:12 ` Andrew Lunn
2014-02-24 18:01 ` [PATCH v2 4/5] ARM: mvebu: Add dts file describing " Andrew Lunn
2014-02-24 19:15 ` Jason Cooper
2014-02-24 18:01 ` [PATCH v2 5/5] ARM: mvebu: Add HP T5325 devices to {multi|mvebu}_v5_defconfig Andrew Lunn
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=201402242232.20851.arnd@arndb.de \
--to=arnd@arndb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.