From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
linux-kernel@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Hans de Goede <hdegoede@redhat.com>
Subject: Re: [PATCH 1/2] device property: export code duplicating array of property entries
Date: Mon, 23 Jan 2017 16:39:07 +0200 [thread overview]
Message-ID: <20170123143907.GU17297@lahna.fi.intel.com> (raw)
In-Reply-To: <20170123073849.28352-1-dmitry.torokhov@gmail.com>
On Sun, Jan 22, 2017 at 11:38:48PM -0800, Dmitry Torokhov wrote:
> When augmenting ACPI-enumerated devices with additional property data based
> on DMI info, a module has often several potential property sets, with only
> one being active on a given box. In order to save memory it should be
> possible to mark everything and __initdata or __initconst, execute DMI
> match early, and duplicate relevant properties. Then kernel will discard
> the rest of them.
>
> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
I think this is good idea, so please feel free to add my,
Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>
next prev parent reply other threads:[~2017-01-23 14:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 7:38 [PATCH 1/2] device property: export code duplicating array of property entries Dmitry Torokhov
2017-01-23 7:38 ` [PATCH 2/2] device property: allow constify properties Dmitry Torokhov
2017-01-23 14:40 ` Mika Westerberg
2017-01-23 15:01 ` Andy Shevchenko
2017-01-23 14:39 ` Mika Westerberg [this message]
2017-01-23 15:00 ` [PATCH 1/2] device property: export code duplicating array of property entries Andy Shevchenko
2017-01-23 22:46 ` Dmitry Torokhov
2017-01-30 22:48 ` Rafael J. Wysocki
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=20170123143907.GU17297@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.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.