From: Marc Zyngier <maz@kernel.org>
To: <Conor.Dooley@microchip.com>
Cc: <helgaas@kernel.org>, <pali@kernel.org>,
<johan+linaro@kernel.org>, <kishon@ti.com>,
<songxiaowei@hisilicon.com>, <wangbinghui@hisilicon.com>,
<thierry.reding@gmail.com>, <ryder.lee@mediatek.com>,
<jianjun.wang@mediatek.com>, <linux-pci@vger.kernel.org>,
<kw@linux.com>, <ley.foon.tan@intel.com>,
<linux-kernel@vger.kernel.org>, <Daire.McNamara@microchip.com>
Subject: Re: Why set .suppress_bind_attrs even though .remove() implemented?
Date: Tue, 26 Jul 2022 08:26:43 +0100 [thread overview]
Message-ID: <87y1wgbah8.wl-maz@kernel.org> (raw)
In-Reply-To: <e3fb313a-f634-3429-05ea-ebaa98809c71@microchip.com>
On Mon, 25 Jul 2022 18:49:05 +0100,
<Conor.Dooley@microchip.com> wrote:
>
> Sorry to butt back in here - but I am taking this to mean that rather
> than add a remove callback for the microchip pci controller driver when
> making it buildable as a module it would instead be better to forgo that
> entirely and prevent unloading the module (since it does INTX & MSI).
>
> Would that be an accurate assessment?
Yes.
M.
--
Without deviation from the norm, progress is not possible.
prev parent reply other threads:[~2022-07-26 7:30 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 19:54 Why set .suppress_bind_attrs even though .remove() implemented? Bjorn Helgaas
2022-07-21 20:46 ` Pali Rohár
2022-07-21 20:48 ` Conor.Dooley
2022-07-21 22:21 ` Bjorn Helgaas
2022-07-21 22:48 ` Pali Rohár
2022-07-22 13:26 ` Johan Hovold
2022-07-22 14:38 ` Bjorn Helgaas
2022-07-25 13:25 ` Johan Hovold
2022-07-25 14:43 ` Marc Zyngier
2022-07-25 15:18 ` Johan Hovold
2022-07-25 17:35 ` Marc Zyngier
2022-07-26 9:56 ` Johan Hovold
2022-07-27 19:57 ` Bjorn Helgaas
2022-07-28 12:17 ` Johan Hovold
2024-10-17 5:23 ` Manivannan Sadhasivam
2024-10-17 7:50 ` Marc Zyngier
2024-10-17 8:25 ` Manivannan Sadhasivam
2024-10-17 8:48 ` Marc Zyngier
2024-10-17 9:30 ` Manivannan Sadhasivam
2024-10-17 9:56 ` Marc Zyngier
2022-09-27 15:27 ` Lorenzo Pieralisi
2022-09-28 6:36 ` Johan Hovold
2022-07-22 14:39 ` Bjorn Helgaas
2022-07-22 17:06 ` Marc Zyngier
2022-07-22 17:17 ` Bjorn Helgaas
2022-07-24 9:38 ` Marc Zyngier
2022-07-25 20:18 ` Florian Fainelli
2022-07-25 17:49 ` Conor.Dooley
2022-07-26 7:26 ` Marc Zyngier [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=87y1wgbah8.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=Conor.Dooley@microchip.com \
--cc=Daire.McNamara@microchip.com \
--cc=helgaas@kernel.org \
--cc=jianjun.wang@mediatek.com \
--cc=johan+linaro@kernel.org \
--cc=kishon@ti.com \
--cc=kw@linux.com \
--cc=ley.foon.tan@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=pali@kernel.org \
--cc=ryder.lee@mediatek.com \
--cc=songxiaowei@hisilicon.com \
--cc=thierry.reding@gmail.com \
--cc=wangbinghui@hisilicon.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox