linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] arm: dts: Add gta04a5 model
Date: Fri, 1 Aug 2014 01:02:46 -0700	[thread overview]
Message-ID: <20140801080246.GG29045@atomide.com> (raw)
In-Reply-To: <CABxcv=n7g8c2ePGKgu_0Y35iearcRoAj9ZH5jDWY9nE+1uUKnA@mail.gmail.com>

* Javier Martinez Canillas <javier@dowhile0.org> [140729 07:14]:
> Hello,
> 
> On Tue, Jul 29, 2014 at 3:03 PM, Dr. H. Nikolaus Schaller
> <hns@goldelico.com> wrote:
> > Hi,
> >> So what's the conclusion? Are changes needed to this patch
> >> series or not?
> >
> > I advocate that no changes are needed.
> >
> 
> I agree with Dr. H. Nikolaus on this regard. A DeviceTree should be a
> description of the hardware and if two hardware platforms differs,
> then we need two different DTS.
> 
> Lately I'm seeing some attempts to abuse u-boot's fdt command, u-boot
> should only modify the strictly necessary like the /chosen branch.
> Allowing u-boot to mangle the FDT before passing to the kernel just to
> avoid some DT duplication doesn't sound like a good idea IMHO.

OK no more comments, so applied all into omap-for-v3.17/dt.
As there's a good chance the merge window will open on Monday,
no guarantees the gta04 related changes will make it. But I'll
send a pull request a bit later on today for them anyways.

Regards,

Tony

      reply	other threads:[~2014-08-01  8:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-28 19:53 [PATCH 0/3] arm: dts: omap3-gta04: Move common parts to include file and add models Marek Belisko
2014-07-28 19:53 ` [PATCH 1/3] arm: dts: omap3-gta04: Rename gta04.dts to gta04.dtsi and add a4 model Marek Belisko
2014-07-28 19:53 ` [PATCH 2/3] arm: dts: Add gta04a3 model Marek Belisko
2014-07-28 19:53 ` [PATCH 3/3] arm: dts: Add gta04a5 model Marek Belisko
     [not found]   ` <CAOf5uwk=ctww=pP4Ae+1C6i-oOtiYTv2NJbj1GpuPwVSKXB4Hw@mail.gmail.com>
2014-07-28 20:02     ` Belisko Marek
     [not found]       ` <CAOf5uw=Fm9FXEH5ESqDC8pGjMbn5VQ1+MyPJVXSqGh_9+JRLHw@mail.gmail.com>
2014-07-28 20:06         ` Belisko Marek
     [not found]           ` <CAOf5uwmjznuK_1au1HnsnYh=BhqC=x+O_tpk6U71bqPv=hFe_A@mail.gmail.com>
2014-07-29  5:17             ` Dr. H. Nikolaus Schaller
2014-07-28 20:42         ` Dr. H. Nikolaus Schaller
2014-07-29 12:41           ` Tony Lindgren
2014-07-29 13:03             ` Dr. H. Nikolaus Schaller
2014-07-29 14:12               ` Javier Martinez Canillas
2014-08-01  8:02                 ` Tony Lindgren [this message]

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=20140801080246.GG29045@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).