From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: Zhangfei Gao <zhangfei.gao@linaro.org>,
Bjorn Helgaas <helgaas@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-pci <linux-pci@vger.kernel.org>
Subject: Re: [PATCH 1/2] PCI: Use software node API with additional device properties
Date: Thu, 30 Sep 2021 13:19:54 +0300 [thread overview]
Message-ID: <CAHp75Vc9hxqy=vrVfuS_cPLCVxZ=KgxZUaD=-rU9W3KH=tAX9Q@mail.gmail.com> (raw)
In-Reply-To: <YVWL3PyYRanGTlVG@kuha.fi.intel.com>
On Thu, Sep 30, 2021 at 1:06 PM Heikki Krogerus
<heikki.krogerus@linux.intel.com> wrote:
> On Thu, Sep 30, 2021 at 10:33:27AM +0800, Zhangfei Gao wrote:
...
> If the device is really never removed, then we could also constify the
> node and the properties in it. Then the patch would look like this:
I'm not sure the user can't force removal of the device (via PCI
rescan, for example,, or via unbind/bind cycle). I guess this way
should be really taken carefully.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-09-30 10:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 13:37 [PATCH 0/2] device property: Remove device_add_properties() Heikki Krogerus
2021-09-29 13:37 ` [PATCH 1/2] PCI: Use software node API with additional device properties Heikki Krogerus
2021-09-29 17:08 ` Bjorn Helgaas
2021-09-30 2:33 ` Zhangfei Gao
2021-09-30 10:05 ` Heikki Krogerus
2021-09-30 10:19 ` Andy Shevchenko [this message]
2021-09-30 10:37 ` Rafael J. Wysocki
2021-09-30 11:26 ` Heikki Krogerus
2021-09-29 13:37 ` [PATCH 2/2] device property: Remove device_add_properties() API Heikki Krogerus
2021-09-29 15:44 ` [PATCH 0/2] device property: Remove device_add_properties() Andy Shevchenko
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='CAHp75Vc9hxqy=vrVfuS_cPLCVxZ=KgxZUaD=-rU9W3KH=tAX9Q@mail.gmail.com' \
--to=andy.shevchenko@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=zhangfei.gao@linaro.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.