From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Tony Lindgren <tony@atomide.com>,
arm@kernel.org, linux-omap@vger.kernel.org
Subject: Re: [GIT PULL 2/2] part 2 of omap dts changes for v3.19
Date: Fri, 28 Nov 2014 14:57:11 +0100 [thread overview]
Message-ID: <201411281457.11648.arnd@arndb.de> (raw)
In-Reply-To: <20141124170908.GF2817@atomide.com>
On Monday 24 November 2014, Tony Lindgren wrote:
> More dts changes for omaps to add support for new devices:
>
> - Add DCAN support am335x, am437x and dra7
>
> - Add devices for sb-t3x computers
>
> - Add support for NovaTech OrionLXm
>
> - Add n900 battery and si4713 support
>
Pulled into next/dt, thanks!
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/2] part 2 of omap dts changes for v3.19
Date: Fri, 28 Nov 2014 14:57:11 +0100 [thread overview]
Message-ID: <201411281457.11648.arnd@arndb.de> (raw)
In-Reply-To: <20141124170908.GF2817@atomide.com>
On Monday 24 November 2014, Tony Lindgren wrote:
> More dts changes for omaps to add support for new devices:
>
> - Add DCAN support am335x, am437x and dra7
>
> - Add devices for sb-t3x computers
>
> - Add support for NovaTech OrionLXm
>
> - Add n900 battery and si4713 support
>
Pulled into next/dt, thanks!
Arnd
next prev parent reply other threads:[~2014-11-28 13:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-23 0:44 [GIT PULL 1/2] part 2 of omap soc changes for v3.19 Tony Lindgren
2014-11-23 0:44 ` [GIT PULL 2/2] part 2 of omap dts " Tony Lindgren
2014-11-23 0:44 ` Tony Lindgren
2014-11-23 0:44 ` Tony Lindgren
2014-11-24 17:09 ` Tony Lindgren
2014-11-24 17:09 ` Tony Lindgren
2014-11-28 13:57 ` Arnd Bergmann [this message]
2014-11-28 13:57 ` Arnd Bergmann
2014-11-28 13:54 ` [GIT PULL 1/2] part 2 of omap soc " Arnd Bergmann
2014-11-28 13:54 ` Arnd Bergmann
2014-11-28 20:22 ` Tony Lindgren
2014-11-28 20:22 ` Tony Lindgren
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=201411281457.11648.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
/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.