public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <mike@compulab.co.il>
To: linux-omap@vger.kernel.org
Cc: Mike Rapoport <mike@compulab.co.il>
Subject: Re: [PATCH 0/2 v2] ARM: OMAP3: add support for cm-t35 board
Date: Mon, 19 Oct 2009 15:59:24 +0200	[thread overview]
Message-ID: <4ADC70BC.1060002@compulab.co.il> (raw)
In-Reply-To: <cover.1255505874.git.mike@compulab.co.il>

Mike Rapoport wrote:
> The following patches add support for CompuLab CM-T35 board.

Any comments on these?

> --
> v2 changes:
>  remove EHCI-related code
>  move usb_musb_init to cm_t35_init
> --
> 
> Changes since commit 2caa731819a633bec5a56736e64c562b7e193666:
>   Linus Torvalds (1):
>           Merge branch 'for-linus' of git://git.kernel.org/.../jbarnes/pci-2.6
> 
> Mike Rapoport (2):
>   ARM: OMAP3: add CompuLab CM-T35 module
>   ARM: OMAP3: cm-t35: add defconfig
> 
>  arch/arm/configs/cm_t35_defconfig  | 1733 ++++++++++++++++++++++++++++++++++++
>  arch/arm/mach-omap2/Kconfig        |    4 +
>  arch/arm/mach-omap2/Makefile       |    2 +
>  arch/arm/mach-omap2/board-cm-t35.c |  459 ++++++++++
>  4 files changed, 2198 insertions(+), 0 deletions(-)
>  create mode 100644 arch/arm/configs/cm_t35_defconfig
>  create mode 100644 arch/arm/mach-omap2/board-cm-t35.c



-- 
Sincerely yours,
Mike.


  parent reply	other threads:[~2009-10-19 13:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-14  7:48 [PATCH 0/2 v2] ARM: OMAP3: add support for cm-t35 board Mike Rapoport
2009-10-14  7:48 ` [PATCH 1/2] ARM: OMAP3: add CompuLab CM-T35 module Mike Rapoport
2009-10-19 17:58   ` Tony Lindgren
2009-10-14  7:48 ` [PATCH 2/2] ARM: OMAP3: cm-t35: add defconfig Mike Rapoport
2009-10-19 13:59 ` Mike Rapoport [this message]
2009-10-19 17:59   ` [PATCH 0/2 v2] ARM: OMAP3: add support for cm-t35 board Tony Lindgren
2009-10-20  6:27     ` Mike Rapoport
2009-10-20 17:39       ` 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=4ADC70BC.1060002@compulab.co.il \
    --to=mike@compulab.co.il \
    --cc=linux-omap@vger.kernel.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