All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
	devicetree@vger.kernel.org, Frank Rowand <frowand.list@gmail.com>
Subject: Re: [PATCH 1/2] of: base: add support to get machine model name
Date: Fri, 18 Nov 2016 08:46:51 -0600	[thread overview]
Message-ID: <20161118144651.275xz4gu6jaefhp7@rob-hp-laptop> (raw)
In-Reply-To: <1479396775-32033-1-git-send-email-sudeep.holla@arm.com>

On Thu, Nov 17, 2016 at 03:32:54PM +0000, Sudeep Holla wrote:
> Currently platforms/drivers needing to get the machine model name are
> replicating the same snippet of code. In some case, the OF reference
> counting is either missing or incorrect.
> 
> This patch adds support to read the machine model name either using
> the "model" or the "compatible" property in the device tree root node
> to the core OF/DT code.
> 
> This can be used to remove all the duplicate code snippets doing exactly
> same thing later.
> 
> Cc: Rob Herring <robh+dt@kernel.org>
> Cc: Frank Rowand <frowand.list@gmail.com>
> Cc: Arnd Bergmann <arnd@arndb.de>
> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
> ---
>  drivers/of/base.c  | 32 ++++++++++++++++++++++++++++++++
>  include/linux/of.h |  6 ++++++
>  2 files changed, 38 insertions(+)
> 
> Hi Rob,
> 
> It would be good if we can target this for v4.10, so that we have no
> dependencies to push PATCH 2/2 in v4.11

Applied.

Rob

  parent reply	other threads:[~2016-11-18 14:46 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-17 15:32 [PATCH 1/2] of: base: add support to get machine model name Sudeep Holla
2016-11-17 15:32 ` Sudeep Holla
2016-11-17 15:32 ` [PATCH 2/2] of: base: replace all duplicate code with of_machine_get_model_name Sudeep Holla
2016-11-17 21:00 ` [PATCH 1/2] of: base: add support to get machine model name Frank Rowand
2016-11-17 21:00   ` Frank Rowand
2016-11-17 22:12   ` Frank Rowand
2016-11-17 22:12     ` Frank Rowand
2016-11-18 10:41   ` Sudeep Holla
2016-11-18 10:41     ` Sudeep Holla
2016-11-18 20:22     ` Frank Rowand
2016-11-18 20:22       ` Frank Rowand
2016-11-21 16:05       ` Frank Rowand
2016-11-21 16:05         ` Frank Rowand
2016-11-21 16:23         ` Sudeep Holla
2016-11-21 16:23           ` Sudeep Holla
2016-11-21 19:24           ` Frank Rowand
2016-11-21 19:24             ` Frank Rowand
2016-11-21 20:49             ` Frank Rowand
2016-11-21 20:49               ` Frank Rowand
2016-11-21 16:20       ` Sudeep Holla
2016-11-21 20:21         ` Frank Rowand
2016-11-21 20:21           ` Frank Rowand
2016-11-18 14:46 ` Rob Herring [this message]
2016-11-18 20:00   ` Frank Rowand
2016-11-18 20:00     ` Frank Rowand
2016-11-22 18:44     ` Frank Rowand
2016-11-22 18:44       ` Frank Rowand
2016-11-22 21:35       ` Rob Herring
2016-11-23 10:25         ` Sudeep Holla
2016-12-09 16:03           ` Rob Herring
2016-12-09 23:54             ` Frank Rowand
2016-12-09 23:54               ` Frank Rowand
2016-12-12 15:17               ` Rob Herring
2016-12-12 15:17                 ` Rob Herring
2016-11-23 10:23       ` Sudeep Holla

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=20161118144651.275xz4gu6jaefhp7@rob-hp-laptop \
    --to=robh@kernel.org \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=frowand.list@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sudeep.holla@arm.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.