From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Uwe Kleine-König" <uwe@kleine-koenig.org>
Cc: "Michael Ellerman" <mpe@ellerman.id.au>,
"Benjamin Herrenschmidt" <benh@kernel.crashing.org>,
"Paul Mackerras" <paulus@samba.org>,
"David S. Miller" <davem@davemloft.net>,
"Jens Axboe" <axboe@kernel.dk>, "Matt Mackall" <mpm@selenic.com>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"Peter Huewe" <peterhuewe@gmx.de>,
"Jarkko Sakkinen" <jarkko@kernel.org>,
"Jason Gunthorpe" <jgg@ziepe.ca>,
"Haren Myneni" <haren@us.ibm.com>,
"Breno Leitão" <leitao@debian.org>,
"Nayna Jain" <nayna@linux.ibm.com>,
"Paulo Flabiano Smorigo" <pfsmorigo@gmail.com>,
"Steven Royer" <seroyer@linux.ibm.com>,
"Arnd Bergmann" <arnd@arndb.de>,
"Cristobal Forno" <cforno12@linux.ibm.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Dany Madden" <drt@linux.ibm.com>,
"Lijun Pan" <ljp@linux.ibm.com>,
"Sukadev Bhattiprolu" <sukadev@linux.ibm.com>,
"Tyrel Datwyler" <tyreld@linux.ibm.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"Michael Cyr" <mikecyr@linux.ibm.com>,
"Jiri Slaby" <jirislaby@kernel.org>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
sparclinux@vger.kernel.org, linux-block@vger.kernel.org,
linux-crypto@vger.kernel.org, linux-integrity@vger.kernel.org,
netdev@vger.kernel.org, linux-scsi@vger.kernel.org,
target-devel@vger.kernel.org
Subject: Re: [PATCH] vio: make remove callback return void
Date: Thu, 4 Feb 2021 17:08:46 +0100 [thread overview]
Message-ID: <YBwcDmtefa2WmS90@kroah.com> (raw)
In-Reply-To: <20210127215010.99954-1-uwe@kleine-koenig.org>
On Wed, Jan 27, 2021 at 10:50:10PM +0100, Uwe Kleine-König wrote:
> The driver core ignores the return value of struct bus_type::remove()
> because there is only little that can be done. To simplify the quest to
> make this function return void, let struct vio_driver::remove() return
> void, too. All users already unconditionally return 0, this commit makes
> it obvious that returning an error code is a bad idea and makes it
> obvious for future driver authors that returning an error code isn't
> intended.
>
> Note there are two nominally different implementations for a vio bus:
> one in arch/sparc/kernel/vio.c and the other in
> arch/powerpc/platforms/pseries/vio.c. I didn't care to check which
> driver is using which of these busses (or if even some of them can be
> used with both) and simply adapt all drivers and the two bus codes in
> one go.
>
> Note that for the powerpc implementation there is a semantical change:
> Before this patch for a device that was bound to a driver without a
> remove callback vio_cmo_bus_remove(viodev) wasn't called. As the device
> core still considers the device unbound after vio_bus_remove() returns
> calling this unconditionally is the consistent behaviour which is
> implemented here.
>
> Signed-off-by: Uwe Kleine-König <uwe@kleine-koenig.org>
> ---
> Hello,
>
> note that this change depends on
> https://lore.kernel.org/r/20210121062005.53271-1-ljp@linux.ibm.com which removes
> an (ignored) return -EBUSY in drivers/net/ethernet/ibm/ibmvnic.c.
> I don't know when/if this latter patch will be applied, so it might take
> some time until my patch can go in.
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Uwe Kleine-König" <uwe@kleine-koenig.org>
Cc: "Cristobal Forno" <cforno12@linux.ibm.com>,
"Tyrel Datwyler" <tyreld@linux.ibm.com>,
sparclinux@vger.kernel.org, target-devel@vger.kernel.org,
"Paul Mackerras" <paulus@samba.org>,
"Breno Leitão" <leitao@debian.org>,
"Peter Huewe" <peterhuewe@gmx.de>,
"Sukadev Bhattiprolu" <sukadev@linux.ibm.com>,
"Jiri Slaby" <jirislaby@kernel.org>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
linux-scsi@vger.kernel.org, "Nayna Jain" <nayna@linux.ibm.com>,
"Jason Gunthorpe" <jgg@ziepe.ca>,
"Michael Cyr" <mikecyr@linux.ibm.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
linux-block@vger.kernel.org, "Lijun Pan" <ljp@linux.ibm.com>,
"Matt Mackall" <mpm@selenic.com>, "Jens Axboe" <axboe@kernel.dk>,
"Steven Royer" <seroyer@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
"Jarkko Sakkinen" <jarkko@kernel.org>,
linux-crypto@vger.kernel.org, "Dany Madden" <drt@linux.ibm.com>,
"Paulo Flabiano Smorigo" <pfsmorigo@gmail.com>,
linux-integrity@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH] vio: make remove callback return void
Date: Thu, 4 Feb 2021 17:08:46 +0100 [thread overview]
Message-ID: <YBwcDmtefa2WmS90@kroah.com> (raw)
In-Reply-To: <20210127215010.99954-1-uwe@kleine-koenig.org>
On Wed, Jan 27, 2021 at 10:50:10PM +0100, Uwe Kleine-König wrote:
> The driver core ignores the return value of struct bus_type::remove()
> because there is only little that can be done. To simplify the quest to
> make this function return void, let struct vio_driver::remove() return
> void, too. All users already unconditionally return 0, this commit makes
> it obvious that returning an error code is a bad idea and makes it
> obvious for future driver authors that returning an error code isn't
> intended.
>
> Note there are two nominally different implementations for a vio bus:
> one in arch/sparc/kernel/vio.c and the other in
> arch/powerpc/platforms/pseries/vio.c. I didn't care to check which
> driver is using which of these busses (or if even some of them can be
> used with both) and simply adapt all drivers and the two bus codes in
> one go.
>
> Note that for the powerpc implementation there is a semantical change:
> Before this patch for a device that was bound to a driver without a
> remove callback vio_cmo_bus_remove(viodev) wasn't called. As the device
> core still considers the device unbound after vio_bus_remove() returns
> calling this unconditionally is the consistent behaviour which is
> implemented here.
>
> Signed-off-by: Uwe Kleine-König <uwe@kleine-koenig.org>
> ---
> Hello,
>
> note that this change depends on
> https://lore.kernel.org/r/20210121062005.53271-1-ljp@linux.ibm.com which removes
> an (ignored) return -EBUSY in drivers/net/ethernet/ibm/ibmvnic.c.
> I don't know when/if this latter patch will be applied, so it might take
> some time until my patch can go in.
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Uwe Kleine-König" <uwe@kleine-koenig.org>
Cc: "Michael Ellerman" <mpe@ellerman.id.au>,
"Benjamin Herrenschmidt" <benh@kernel.crashing.org>,
"Paul Mackerras" <paulus@samba.org>,
"David S. Miller" <davem@davemloft.net>,
"Jens Axboe" <axboe@kernel.dk>, "Matt Mackall" <mpm@selenic.com>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"Peter Huewe" <peterhuewe@gmx.de>,
"Jarkko Sakkinen" <jarkko@kernel.org>,
"Jason Gunthorpe" <jgg@ziepe.ca>,
"Haren Myneni" <haren@us.ibm.com>,
"Breno Leitão" <leitao@debian.org>,
"Nayna Jain" <nayna@linux.ibm.com>,
"Paulo Flabiano Smorigo" <pfsmorigo@gmail.com>,
"Steven Royer" <seroyer@linux.ibm.com>,
"Arnd Bergmann" <arnd@arndb.de>,
"Cristobal Forno" <cforno12@linux.ibm.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Dany Madden" <drt@linux.ibm.com>,
"Lijun Pan" <ljp@linux.ibm.com>,
"Sukadev Bhattiprolu" <sukadev@linux.ibm.com>,
"Tyrel Datwyler" <tyreld@linux.ibm.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"Michael Cyr" <mikecyr@linux.ibm.com>,
"Jiri Slaby" <jirislaby@kernel.org>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
sparclinux@vger.kernel.org, linux-block@vger.kernel.org,
linux-crypto@vger.kernel.org, linux-integrity@vger.kernel.org,
netdev@vger.kernel.org, linux-scsi@vger.kernel.org,
target-devel@vger.kernel.org
Subject: Re: [PATCH] vio: make remove callback return void
Date: Thu, 04 Feb 2021 16:08:46 +0000 [thread overview]
Message-ID: <YBwcDmtefa2WmS90@kroah.com> (raw)
In-Reply-To: <20210127215010.99954-1-uwe@kleine-koenig.org>
On Wed, Jan 27, 2021 at 10:50:10PM +0100, Uwe Kleine-König wrote:
> The driver core ignores the return value of struct bus_type::remove()
> because there is only little that can be done. To simplify the quest to
> make this function return void, let struct vio_driver::remove() return
> void, too. All users already unconditionally return 0, this commit makes
> it obvious that returning an error code is a bad idea and makes it
> obvious for future driver authors that returning an error code isn't
> intended.
>
> Note there are two nominally different implementations for a vio bus:
> one in arch/sparc/kernel/vio.c and the other in
> arch/powerpc/platforms/pseries/vio.c. I didn't care to check which
> driver is using which of these busses (or if even some of them can be
> used with both) and simply adapt all drivers and the two bus codes in
> one go.
>
> Note that for the powerpc implementation there is a semantical change:
> Before this patch for a device that was bound to a driver without a
> remove callback vio_cmo_bus_remove(viodev) wasn't called. As the device
> core still considers the device unbound after vio_bus_remove() returns
> calling this unconditionally is the consistent behaviour which is
> implemented here.
>
> Signed-off-by: Uwe Kleine-König <uwe@kleine-koenig.org>
> ---
> Hello,
>
> note that this change depends on
> https://lore.kernel.org/r/20210121062005.53271-1-ljp@linux.ibm.com which removes
> an (ignored) return -EBUSY in drivers/net/ethernet/ibm/ibmvnic.c.
> I don't know when/if this latter patch will be applied, so it might take
> some time until my patch can go in.
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
next prev parent reply other threads:[~2021-02-04 16:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 21:50 [PATCH] vio: make remove callback return void Uwe Kleine-König
2021-01-27 21:50 ` Uwe Kleine-König
2021-01-27 21:50 ` Uwe Kleine-König
2021-01-28 19:07 ` Sukadev Bhattiprolu
2021-01-28 20:08 ` Uwe Kleine-König
2021-01-28 20:08 ` Uwe Kleine-König
2021-01-28 20:08 ` Uwe Kleine-König
2021-01-29 18:58 ` Tyrel Datwyler
2021-01-29 18:58 ` Tyrel Datwyler
2021-01-29 18:58 ` Tyrel Datwyler
2021-01-29 19:08 ` Lijun Pan
2021-01-29 19:08 ` Lijun Pan
2021-01-29 19:08 ` Lijun Pan
2021-02-04 16:08 ` Greg Kroah-Hartman [this message]
2021-02-04 16:08 ` Greg Kroah-Hartman
2021-02-04 16:08 ` Greg Kroah-Hartman
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=YBwcDmtefa2WmS90@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=benh@kernel.crashing.org \
--cc=cforno12@linux.ibm.com \
--cc=davem@davemloft.net \
--cc=drt@linux.ibm.com \
--cc=haren@us.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=jarkko@kernel.org \
--cc=jejb@linux.ibm.com \
--cc=jgg@ziepe.ca \
--cc=jirislaby@kernel.org \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=ljp@linux.ibm.com \
--cc=martin.petersen@oracle.com \
--cc=mikecyr@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=mpm@selenic.com \
--cc=nayna@linux.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=paulus@samba.org \
--cc=peterhuewe@gmx.de \
--cc=pfsmorigo@gmail.com \
--cc=seroyer@linux.ibm.com \
--cc=sparclinux@vger.kernel.org \
--cc=sukadev@linux.ibm.com \
--cc=target-devel@vger.kernel.org \
--cc=tyreld@linux.ibm.com \
--cc=uwe@kleine-koenig.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.