From: Tony Lindgren <tony@atomide.com>
To: Felipe Balbi <balbi@ti.com>
Cc: Sergei Shtylyov <sshtylyov@mvista.com>,
Jan Weitzel <j.weitzel@phytec.de>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] ARM: OMAP4: Add pcm049 to Kconfig/Makefile
Date: Thu, 14 Jul 2011 00:27:08 -0700 [thread overview]
Message-ID: <20110714072708.GK5783@atomide.com> (raw)
In-Reply-To: <20110708115842.GJ4820@legolas.emea.dhcp.ti.com>
* Felipe Balbi <balbi@ti.com> [110708 04:53]:
>
> Are you or are you not taking now board files ? We have one which was
> left out due to a comment from Russell stating that no new board-files
> would be accepted until the move to device tree was completed [1]
Well looking at the cumulative diffstats, adding these board files
with about total of 1000 lines of addition would push our diffstat to
positive side. And that's not a good sign of code coalescing.
So I'll carry the board files in testing-board until we have device tree
working and won't need those.
Alternatively if somebody combines beagle variants to use board-beagle-common.c
and board-panda-common.c then adding new boards would have minimal impact
and would probably make device tree conversion of these boards easier
too.
Regards,
Tony
> [1] http://marc.info/?t=130199607500006&r=1&w=2
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] ARM: OMAP4: Add pcm049 to Kconfig/Makefile
Date: Thu, 14 Jul 2011 00:27:08 -0700 [thread overview]
Message-ID: <20110714072708.GK5783@atomide.com> (raw)
In-Reply-To: <20110708115842.GJ4820@legolas.emea.dhcp.ti.com>
* Felipe Balbi <balbi@ti.com> [110708 04:53]:
>
> Are you or are you not taking now board files ? We have one which was
> left out due to a comment from Russell stating that no new board-files
> would be accepted until the move to device tree was completed [1]
Well looking at the cumulative diffstats, adding these board files
with about total of 1000 lines of addition would push our diffstat to
positive side. And that's not a good sign of code coalescing.
So I'll carry the board files in testing-board until we have device tree
working and won't need those.
Alternatively if somebody combines beagle variants to use board-beagle-common.c
and board-panda-common.c then adding new boards would have minimal impact
and would probably make device tree conversion of these boards easier
too.
Regards,
Tony
> [1] http://marc.info/?t=130199607500006&r=1&w=2
next prev parent reply other threads:[~2011-07-14 7:27 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-08 10:04 [PATCH 0/3] ARM:OMAP4 add Phytec phyCORE-OMAP4 board Jan Weitzel
2011-07-08 10:04 ` Jan Weitzel
2011-07-08 10:04 ` [PATCH 1/3] ARM: OMAP4: Add pcm049 to Kconfig/Makefile Jan Weitzel
2011-07-08 10:04 ` Jan Weitzel
2011-07-08 11:49 ` Sergei Shtylyov
2011-07-08 11:49 ` Sergei Shtylyov
2011-07-08 11:55 ` Tony Lindgren
2011-07-08 11:55 ` Tony Lindgren
2011-07-08 11:58 ` Felipe Balbi
2011-07-08 11:58 ` Felipe Balbi
2011-07-14 7:27 ` Tony Lindgren [this message]
2011-07-14 7:27 ` Tony Lindgren
2011-07-14 7:47 ` Tony Lindgren
2011-07-14 7:47 ` Tony Lindgren
2011-07-08 12:21 ` [PATCH v2] ARM:OMAP4 add Phytec phyCORE-OMAP4 board Jan Weitzel
2011-07-08 12:21 ` Jan Weitzel
2011-07-13 8:03 ` Tony Lindgren
2011-07-13 8:03 ` Tony Lindgren
2011-07-13 10:58 ` Jan Weitzel
2011-07-13 10:58 ` Jan Weitzel
2011-07-13 10:59 ` [PATCH] ARM: OMAP4: PCM049: remove vusim regulator Jan Weitzel
2011-07-13 10:59 ` Jan Weitzel
2011-07-13 12:13 ` Sergei Shtylyov
2011-07-13 12:13 ` Sergei Shtylyov
2011-07-13 12:54 ` [PATCH v2] " Jan Weitzel
2011-07-13 12:54 ` Jan Weitzel
2011-07-13 12:56 ` [PATCH] " Jan Weitzel
2011-07-13 12:56 ` Jan Weitzel
2011-07-14 7:34 ` Tony Lindgren
2011-07-14 7:34 ` Tony Lindgren
2011-07-14 8:39 ` Jan Weitzel
2011-07-14 8:39 ` Jan Weitzel
2011-07-15 7:50 ` Tony Lindgren
2011-07-15 7:50 ` Tony Lindgren
2011-07-15 7:58 ` Felipe Balbi
2011-07-15 7:58 ` Felipe Balbi
2011-07-15 8:20 ` Tony Lindgren
2011-07-15 8:20 ` Tony Lindgren
2011-07-15 8:31 ` Felipe Balbi
2011-07-15 8:31 ` Felipe Balbi
2011-07-15 10:59 ` Tony Lindgren
2011-07-15 10:59 ` Tony Lindgren
2011-07-15 9:47 ` Jan Weitzel
2011-07-15 9:47 ` Jan Weitzel
2011-07-15 10:55 ` Tony Lindgren
2011-07-15 10:55 ` Tony Lindgren
2011-07-15 16:06 ` [RFC 0/2] join omap4panda and pcm049 Jan Weitzel
2011-07-18 8:42 ` Tony Lindgren
2011-07-19 11:45 ` [RFC 0/2 v2] " Jan Weitzel
2011-07-19 11:45 ` [RFC 1/2] omap4: board-omap4panda: prepare for join Jan Weitzel
2011-07-21 7:25 ` Tony Lindgren
2011-07-19 11:45 ` [RFC 2/2] omap4: board-omap4pcm049: add Phytec phyCORE-OMAP4 Jan Weitzel
2011-07-21 7:38 ` Tony Lindgren
2011-07-15 16:06 ` [PATCH 1/2] omap4: board-omap4panda: prepare for join Jan Weitzel
2011-07-15 16:06 ` [PATCH 2/2] omap4: board-omap4panda: join Phytec phyCORE-OMAP4 Jan Weitzel
2011-07-08 10:04 ` [PATCH 2/3] ARM: OMAP4: add pcm049 DEBUGLL Jan Weitzel
2011-07-08 10:04 ` Jan Weitzel
2011-07-08 10:04 ` [PATCH 3/3] ARM: OMAP4: platformcode board-omap4pcm049.c Jan Weitzel
2011-07-08 10:04 ` Jan Weitzel
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=20110714072708.GK5783@atomide.com \
--to=tony@atomide.com \
--cc=balbi@ti.com \
--cc=j.weitzel@phytec.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=sshtylyov@mvista.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.