From: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Marc Titinger <mtitinger-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
Cc: lina.iyer-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
ahaslam-rdvid1DuHRBWk0Htik3J/w@public.gmane.org,
Kumar Gala <galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 19/26] devicetree: bindings: Document qcom,msm-id and qcom,board-id
Date: Fri, 18 Dec 2015 22:17:28 -0600 [thread overview]
Message-ID: <20151219041728.GD14936@rob-hp-laptop> (raw)
In-Reply-To: <1450371534-10923-20-git-send-email-mtitinger+renesas-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
On Thu, Dec 17, 2015 at 05:58:47PM +0100, Marc Titinger wrote:
> From: Kumar Gala <galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
>
> The top level qcom,msm-id and qcom,board-id are utilized by bootloaders
> on Qualcomm MSM platforms to determine which device tree should be
> utilized and passed to the kernel.
>
> Cc: <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
> Signed-off-by: Kumar Gala <galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
Nak. Stephen Boyd has already done an alternative.
Rob
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-12-19 4:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1450371534-10923-1-git-send-email-mtitinger+renesas@baylibre.com>
[not found] ` <1450371534-10923-1-git-send-email-mtitinger+renesas-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
[not found] ` <20151216222941.GB3342-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-12-17 16:58 ` [PATCH 19/26] devicetree: bindings: Document qcom,msm-id and qcom,board-id Marc Titinger
[not found] ` <1450371534-10923-20-git-send-email-mtitinger+renesas-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
2015-12-19 4:17 ` Rob Herring [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=20151219041728.GD14936@rob-hp-laptop \
--to=robh-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=ahaslam-rdvid1DuHRBWk0Htik3J/w@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=lina.iyer-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=mtitinger-rdvid1DuHRBWk0Htik3J/w@public.gmane.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