From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Vivek Gautam <vivek.gautam@codeaurora.org>
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Greg KH <gregkh@linuxfoundation.org>,
lukas@wunner.de, dmitry.torokhov@gmail.com, aspriel@gmail.com,
Robin Murphy <robin.murphy@arm.com>,
open list <linux-kernel@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>
Subject: Re: [PATCH 1/1] device core: Add flag to autoremove device link on supplier unbind
Date: Tue, 26 Jun 2018 12:19:20 +0200 [thread overview]
Message-ID: <6354476.UjADPVylrh@aspire.rjw.lan> (raw)
In-Reply-To: <CAFp+6iGwcbOm0p33o9NEE7YBZNNvRsBeU0ySy0HcEmvq8mhBJA@mail.gmail.com>
On Tuesday, June 26, 2018 12:03:44 PM CEST Vivek Gautam wrote:
> On Wed, May 30, 2018 at 6:21 PM, Vivek Gautam
> <vivek.gautam@codeaurora.org> wrote:
>
> Adding Ulf and Marek for their side of comments.
> In summary, we do not want to not maintain a device link pointer
> when adding a device link in supplier's driver, to delete the link later.
> An autoremove flag from the suppliers side (similar to what we already
> have for consumer side) can help autoremove the device link
> when supplier driver goes away.
>
> Hi Rafael, Lukas,
> Gentle ping. Can you please consider reviewing this patch.
ISTR telling you that I didn't like the DL_FLAG_AUTOREMOVE_S name
as it is too similar to another existing flag. That hasn't changed.
BTW, please CC the patch to linux-pm when you resend it.
Thanks,
Rafael
next prev parent reply other threads:[~2018-06-26 10:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180530095704.5788-1-vivek.gautam@codeaurora.org>
2018-05-30 10:59 ` [PATCH 1/1] device core: Add flag to autoremove device link on supplier unbind Rafael J. Wysocki
2018-05-30 12:51 ` Vivek Gautam
2018-06-26 10:03 ` Vivek Gautam
2018-06-26 10:19 ` Rafael J. Wysocki [this message]
2018-06-26 11:48 ` Vivek Gautam
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=6354476.UjADPVylrh@aspire.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=aspriel@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=m.szyprowski@samsung.com \
--cc=rafael.j.wysocki@intel.com \
--cc=robin.murphy@arm.com \
--cc=ulf.hansson@linaro.org \
--cc=vivek.gautam@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox