linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: nm@ti.com (Nishanth Menon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 0/2] ARM: OMAP2+/dts: standardize SoC naming
Date: Wed, 4 Dec 2013 18:49:35 -0600	[thread overview]
Message-ID: <1386204578-6018-1-git-send-email-nm@ti.com> (raw)

Originally attempted partially in [1], the missing binding were
reported as part of Rob's report in [2].

So, here is take two of the series, lacking an standard causes issues
that was fixed such as [3]. Ideally, we should never again introduce a
board file without a exact compatible SoC match.

I have stayed a bit away from updating board and SoC dts files yet
to look at the direction we'd like to go here. If we feel things are
good, I would gladly try to clean our mess up.

Nishanth Menon (2):
  Documentation: dt: OMAP: explicitly state SoC compatible strings
  ARM: OMAP2+: board-generic: update SoC compatibility strings

 .../devicetree/bindings/arm/omap/omap.txt          |   53 ++++++++++++++++++++
 arch/arm/mach-omap2/board-generic.c                |    7 +++
 2 files changed, 60 insertions(+)

[1] https://patchwork.kernel.org/patch/2998201/
[2] http://marc.info/?l=linux-arm-kernel&m=138378029113665&w=2
[3] https://patchwork.kernel.org/patch/3279281/

-- 
1.7.9.5

             reply	other threads:[~2013-12-05  0:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-05  0:49 Nishanth Menon [this message]
2013-12-05  0:49 ` [PATCH V2 1/2] Documentation: dt: OMAP: explicitly state SoC compatible strings Nishanth Menon
2013-12-05  0:49 ` [PATCH V2 2/2] ARM: OMAP2+: board-generic: update SoC compatibility strings Nishanth Menon
2014-01-07  0:47 ` [PATCH V2 0/2] ARM: OMAP2+/dts: standardize SoC naming Nishanth Menon
2014-01-08 19:18   ` 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=1386204578-6018-1-git-send-email-nm@ti.com \
    --to=nm@ti.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).