From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
John Youn <John.Youn@synopsys.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] device property: fix for couple of bugs
Date: Fri, 26 Feb 2016 10:02:52 +0200 [thread overview]
Message-ID: <20160226080252.GC29434@kuha.fi.intel.com> (raw)
In-Reply-To: <2719908.p6aFAYnX7E@vostro.rjw.lan>
On Wed, Feb 24, 2016 at 12:37:43AM +0100, Rafael J. Wysocki wrote:
> On Monday, February 22, 2016 04:50:39 PM Heikki Krogerus wrote:
> > Hi,
> >
> > The fwnode->secondary is causing problems when a property_set is
> > providing the primary fwnode.
> >
> > Both of these fixes are a bit clumsy looking IMO, but I didn't have
> > better ideas. I think the second one fixing the use-after-free bug
> > should ideally be taken care of in set_secondary_fwnode() instead of
> > device_remove_property_set(), but I didn't have any ideas how to do
> > that.
>
> Can you please CC device property framework patches to linux-acpi?
>
> They are somewhat easier to handle this way.
Will do.
Thanks,
--
heikki
prev parent reply other threads:[~2016-02-26 8:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 14:50 [PATCH 0/2] device property: fix for couple of bugs Heikki Krogerus
2016-02-22 14:50 ` [PATCH 1/2] device property: fwnode->secondary may contain ERR_PTR(-ENODEV) Heikki Krogerus
2016-02-22 14:50 ` [PATCH 2/2] device property: fix for a case of use-after-free Heikki Krogerus
2016-02-22 15:40 ` Andy Shevchenko
2016-02-22 17:04 ` Shevchenko, Andriy
2016-02-23 23:37 ` Rafael J. Wysocki
2016-02-26 8:04 ` Heikki Krogerus
2016-02-26 10:36 ` Heikki Krogerus
2016-02-23 23:37 ` [PATCH 0/2] device property: fix for couple of bugs Rafael J. Wysocki
2016-02-26 8:02 ` Heikki Krogerus [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=20160226080252.GC29434@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=John.Youn@synopsys.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rjw@rjwysocki.net \
/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.