linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Igor Grinberg <grinberg@compulab.co.il>
To: Tony Lindgren <tony@atomide.com>
Cc: Dmitry Lifshitz <lifshitz@compulab.co.il>,
	Benoit Cousson <bcousson@baylibre.com>,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 00/11] ARM: dts: sbc-t3x: add support for more boards
Date: Sun, 02 Mar 2014 16:15:45 +0200	[thread overview]
Message-ID: <53133D11.7000502@compulab.co.il> (raw)
In-Reply-To: <20140228221219.GH13624@atomide.com>

On 03/01/14 00:12, Tony Lindgren wrote:
> * Igor Grinberg <grinberg@compulab.co.il> [140223 04:33]:
>> ping x2!
> 
> Thanks applying into omap-for-v3.15/dt finally.

Thanks!

> 
> Is it OK to remove the board-cm-*.c files for v3.15?

Hmmm....
I thought we will have a transition release with both ways and
similar functionality available...
For this to happen, we need to extend the DT support to the stuff
board-cm-t*.c files cover before removing them...
We should be able to send additional patches in 3-5 weeks.
Since rc4 is out a week ago, and rc5 is coming, we won't be able
to prepare the extension in time for 3.15...
So, can we postpone the board-cm-t*.c files removal to 3.16?
Or does it make too much trouble for you?

-- 
Regards,
Igor.

  reply	other threads:[~2014-03-02 14:16 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-12 13:22 [PATCH 00/11] ARM: dts: sbc-t3x: add support for more boards Dmitry Lifshitz
2014-01-12 13:22 ` [PATCH 01/12] ARM: dts: sbc-t3x: use omap specific pinctrl defines Dmitry Lifshitz
2014-01-12 13:22 ` [PATCH 02/12] ARM: dts: sbc-t3x: refactor DT support Dmitry Lifshitz
2014-01-12 13:22 ` [PATCH 03/12] ARM: dts: sbc-t3x: disable mmc3 Dmitry Lifshitz
2014-01-12 13:22 ` [PATCH 04/12] ARM: dts: sb-t35: fix Ethernet power supply Dmitry Lifshitz
2014-01-12 13:22 ` [PATCH 05/12] ARM: dts: cm-t3x: add gpio-led pinmux Dmitry Lifshitz
2014-01-12 13:22 ` [PATCH 06/12] ARM: dts: cm-t3x30: add twl4030 gpio pullups Dmitry Lifshitz
2014-01-12 13:22 ` [PATCH 07/12] ARM: dts: cm-t3x30: add HS USB Host support Dmitry Lifshitz
2014-01-12 13:22 ` [PATCH 08/12] ARM: dts: sbc-t3730: add pinmux for usb hub reset Dmitry Lifshitz
2014-01-12 13:22 ` [PATCH 09/12] ARM: dts: cm-t3x30: add USB OTG support Dmitry Lifshitz
2014-01-12 13:22 ` [PATCH 10/12] ARM: dts: sbc-t3530: add support for sbc-t3530 Dmitry Lifshitz
2014-01-12 13:22 ` [PATCH 11/12] ARM: dts: sbc-t3517: add support for sbc-t3517 Dmitry Lifshitz
2014-01-12 13:22 ` [PATCH 12/12] ARM: OMAP2+: make reset pulse for sbc-t3x usb hubs Dmitry Lifshitz
2014-01-19  8:48 ` [PATCH 00/12] ARM: dts: sbc-t3x: add support for more boards Dmitry Lifshitz
2014-02-12 12:38 ` [PATCH 00/11] " Igor Grinberg
2014-02-23 12:30   ` Igor Grinberg
2014-02-28 22:12     ` Tony Lindgren
2014-03-02 14:15       ` Igor Grinberg [this message]
2014-03-02 17:07         ` 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=53133D11.7000502@compulab.co.il \
    --to=grinberg@compulab.co.il \
    --cc=bcousson@baylibre.com \
    --cc=lifshitz@compulab.co.il \
    --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 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).