linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	Hans de Goede <hdegoede@redhat.com>,
	Wolfram Sang <wsa@the-dreams.de>
Subject: Re: [PATCH v3 0/4] Export APIs to copy device properties & more
Date: Wed, 1 Feb 2017 14:56:09 -0800	[thread overview]
Message-ID: <20170201225609.GG40720@dtor-ws> (raw)
In-Reply-To: <20170201173125.40354-1-dmitry.torokhov@gmail.com>

On Wed, Feb 01, 2017 at 09:31:21AM -0800, Dmitry Torokhov wrote:
> Hi,
> 
> Here is the refreshed series exporting APIs to copy statically declared
> device properties. The reason is that we want to augment ACPI-based devices
> with properties, and drivers usually have a largish DMI table for multiple
> models, so it is desirable to mark everything as __initdata/__initconst,
> and then copy only the entry matching the device we are running on and
> discard the rest.
> 
> The last patch is not really about device property APIs, but rather
> allowing users to attach properties to i2c_board_info, and have them
> attached to instantiated device(s). The reason it is included is because it
> depends on device_add_properties() taking const pointer, which is patch #2.
> 
> If it seems useful I hope Rafael and Wolfram would figure a way to merge it
> :).

By the way, if this series is accepted, it would be very helpful to have
it in a stable branch off 4.10-rcX as I have more patches to
platform/chrome and Atmel touchscreen driver depending on it.

> 
> v3:
> - fix memory leak in property_copy_string_array() pointed out by Mika
>   Westerberg
> 
> v2:
> - addressed Andy's comments
> - added property_entries_free()
> - added patch to allow constify values of property arrays
> - added i2c patch allowing to attach property to devices via board info
> 
> v1:
> - initial posting
> 
> 
> Dmitry Torokhov (4):
>   device property: export code duplicating array of property entries
>   device property: allow to constify properties
>   driver property: constify property arrays values
>   i2c: allow specify device properties in i2c_board_info
> 
>  drivers/base/property.c  | 222 ++++++++++++++++++++++++++++++-----------------
>  drivers/i2c/i2c-core.c   |  16 +++-
>  include/linux/i2c.h      |   3 +
>  include/linux/property.h |  19 ++--
>  4 files changed, 171 insertions(+), 89 deletions(-)
> 
> Thanks.
> 
> -- 
> Dmitry
> 

-- 
Dmitry

      parent reply	other threads:[~2017-02-01 22:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-01 17:31 [PATCH v3 0/4] Export APIs to copy device properties & more Dmitry Torokhov
2017-02-01 17:31 ` [PATCH v3 1/4] device property: export code duplicating array of property entries Dmitry Torokhov
2017-02-01 17:31 ` [PATCH v3 2/4] device property: allow to constify properties Dmitry Torokhov
2017-02-01 17:31 ` [PATCH v3 3/4] driver property: constify property arrays values Dmitry Torokhov
2017-02-01 23:30   ` Joe Perches
2017-02-02 11:24     ` Rafael J. Wysocki
2017-02-02 16:39       ` [PATCH v4 3/4] device " Dmitry Torokhov
2017-02-02 16:48         ` Andy Shevchenko
2017-02-02 17:07           ` Dmitry Torokhov
2017-02-02 17:52             ` Andy Shevchenko
2017-02-02 18:38               ` Dmitry Torokhov
2017-02-02 23:16                 ` Rafael J. Wysocki
2017-02-03  0:16                   ` Dmitry Torokhov
2017-02-03  0:37                     ` Rafael J. Wysocki
2017-02-03  1:06                       ` Dmitry Torokhov
2017-02-02 10:08   ` [PATCH v3 3/4] driver " Mika Westerberg
2017-02-01 17:31 ` [PATCH v3 4/4] i2c: allow specify device properties in i2c_board_info Dmitry Torokhov
2017-02-02 10:08   ` Mika Westerberg
2017-02-01 22:56 ` Dmitry Torokhov [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=20170201225609.GG40720@dtor-ws \
    --to=dmitry.torokhov@gmail.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=wsa@the-dreams.de \
    /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).