All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-kernel@vger.kernel.org,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	linux-acpi@vger.kernel.org
Subject: Re: [PATCH v1 1/1] device property: Unify access to of_node
Date: Fri, 4 Jun 2021 15:25:38 +0200	[thread overview]
Message-ID: <YLop0g8+ZZt60HYC@kroah.com> (raw)
In-Reply-To: <20210604131343.62016-1-andriy.shevchenko@linux.intel.com>

On Fri, Jun 04, 2021 at 04:13:43PM +0300, Andy Shevchenko wrote:
> Historically we have a few variants how we access dev->fwnode
> and dev->of_node. Some of the functions during development
> gained different versions of the getters. Unify access to of_node
> and as a side change slightly refactor ACPI specific branches.
> 
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
>  drivers/base/property.c  | 29 +++++++++++++----------------
>  include/linux/property.h |  2 +-
>  2 files changed, 14 insertions(+), 17 deletions(-)

Less code and const structures are always a win.  If I get an ack from
Rafael I will merge this in my tree.

thanks,
greg k-h

  reply	other threads:[~2021-06-04 13:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-04 13:13 [PATCH v1 1/1] device property: Unify access to of_node Andy Shevchenko
2021-06-04 13:25 ` Greg Kroah-Hartman [this message]
2021-06-04 14:55 ` kernel test robot
2021-06-04 14:55   ` kernel test robot
2021-06-04 15:55   ` Andy Shevchenko
2021-06-04 15:55     ` Andy Shevchenko
2021-06-04 16:14 ` kernel test robot
2021-06-04 16:14   ` kernel test robot
2021-06-04 16:36   ` Andy Shevchenko
2021-06-04 16:36     ` Andy Shevchenko
2021-06-04 17:29 ` kernel test robot
2021-06-04 17:29   ` kernel test robot

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=YLop0g8+ZZt60HYC@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.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 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.