All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Igor Grinberg <grinberg@compulab.co.il>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	Mike Rapoport <mike@compulab.co.il>
Subject: Re: [PATCH v3 3/3] arm: omap3: cm-t35: add support for cm-t3730
Date: Mon, 27 Jun 2011 03:21:11 -0700	[thread overview]
Message-ID: <20110627102111.GJ23145@atomide.com> (raw)
In-Reply-To: <4E0840E6.7030901@compulab.co.il>

* Igor Grinberg <grinberg@compulab.co.il> [110627 01:31]:
> Tony,
> 
> I'd really like us to decide, because I want my (currently) out of tree port
> to be based on one of the patches (v2 or v3).
> 
> Can you please, look into this?

Sorry for the delay, yes that looks good to me. Will add to devel-board branch.

Regards,

Tony

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 3/3] arm: omap3: cm-t35: add support for cm-t3730
Date: Mon, 27 Jun 2011 03:21:11 -0700	[thread overview]
Message-ID: <20110627102111.GJ23145@atomide.com> (raw)
In-Reply-To: <4E0840E6.7030901@compulab.co.il>

* Igor Grinberg <grinberg@compulab.co.il> [110627 01:31]:
> Tony,
> 
> I'd really like us to decide, because I want my (currently) out of tree port
> to be based on one of the patches (v2 or v3).
> 
> Can you please, look into this?

Sorry for the delay, yes that looks good to me. Will add to devel-board branch.

Regards,

Tony

  reply	other threads:[~2011-06-27 10:21 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-05  8:53 [PATCH] arm: omap3: cm-t35: add support for cm-t3730 Igor Grinberg
2011-05-05  8:53 ` Igor Grinberg
2011-05-05  9:51 ` Mike Rapoport
2011-05-05  9:51   ` Mike Rapoport
2011-05-08  7:20   ` [PATCH v2] " Igor Grinberg
2011-05-08  7:20     ` Igor Grinberg
2011-05-31 13:04     ` Tony Lindgren
2011-05-31 13:04       ` Tony Lindgren
2011-06-03 13:37       ` Igor Grinberg
2011-06-03 13:37         ` Igor Grinberg
2011-06-13 13:33         ` Tony Lindgren
2011-06-13 13:33           ` Tony Lindgren
2011-06-13 19:34           ` Igor Grinberg
2011-06-13 19:34             ` Igor Grinberg
2011-06-14  7:36             ` Tony Lindgren
2011-06-14  7:36               ` Tony Lindgren
2011-06-14 21:16               ` [PATCH 1/3] arm: omap3: cm-t35: minor comments fixes Igor Grinberg
2011-06-14 21:16                 ` Igor Grinberg
2011-06-14 21:16               ` [PATCH 2/3] arm: omap3: cm-t35: fix slow path warning Igor Grinberg
2011-06-14 21:16                 ` Igor Grinberg
2011-06-14 21:16               ` [PATCH v3 3/3] arm: omap3: cm-t35: add support for cm-t3730 Igor Grinberg
2011-06-14 21:16                 ` Igor Grinberg
2011-06-22 14:56                 ` Igor Grinberg
2011-06-22 14:56                   ` Igor Grinberg
2011-06-27  8:35                   ` Igor Grinberg
2011-06-27  8:35                     ` Igor Grinberg
2011-06-27 10:21                     ` Tony Lindgren [this message]
2011-06-27 10:21                       ` Tony Lindgren
2011-06-27 12:31                       ` Igor Grinberg
2011-06-27 12:31                         ` Igor Grinberg

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=20110627102111.GJ23145@atomide.com \
    --to=tony@atomide.com \
    --cc=grinberg@compulab.co.il \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mike@compulab.co.il \
    /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.