dmaengine.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Fenghua Yu <fenghua.yu@intel.com>
Cc: linux-kernel@vger.kernel.org, rafael@kernel.org,
	Dave Jiang <dave.jiang@intel.com>, Vinod Koul <vkoul@kernel.org>,
	dmaengine@vger.kernel.org
Subject: Re: [PATCH 32/36] dmaengine: idxd: use const struct bus_type *
Date: Thu, 16 Mar 2023 11:16:00 +0100	[thread overview]
Message-ID: <ZBLsYNXXCBkb8QlO@kroah.com> (raw)
In-Reply-To: <76db3d98-2d09-54de-ab46-0ec9d743e05d@intel.com>

On Mon, Mar 13, 2023 at 12:07:27PM -0700, Fenghua Yu wrote:
> Hi, Greg,
> 
> On 3/13/23 11:29, Greg Kroah-Hartman wrote:
> > In the functions unbind_store() and bind_store(), a struct bus_type *
> > should be a const one, as the driver core bus functions used by this
> > variable are expecting the pointer to be constant, and these functions
> > do not modify the pointer at all.
> > 
> > Cc: Fenghua Yu <fenghua.yu@intel.com>
> > Cc: Dave Jiang <dave.jiang@intel.com>
> > Cc: Vinod Koul <vkoul@kernel.org>
> > Cc: dmaengine@vger.kernel.org
> > Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > ---
> > Note, this is a patch that is a prepatory cleanup as part of a larger
> > series of patches that is working on resolving some old driver core
> > design mistakes.  It will build and apply cleanly on top of 6.3-rc2 on
> > its own, but I'd prefer if I could take it through my driver-core tree
> > so that the driver core changes can be taken through there for 6.4-rc1.
> > 
> >   drivers/dma/idxd/compat.c | 4 ++--
> >   1 file changed, 2 insertions(+), 2 deletions(-)
> > 
> > diff --git a/drivers/dma/idxd/compat.c b/drivers/dma/idxd/compat.c
> > index 3df21615f888..5fd38d1b9d28 100644
> > --- a/drivers/dma/idxd/compat.c
> > +++ b/drivers/dma/idxd/compat.c
> > @@ -16,7 +16,7 @@ extern void device_driver_detach(struct device *dev);
> >   static ssize_t unbind_store(struct device_driver *drv, const char *buf, size_t count)
> >   {
> > -	struct bus_type *bus = drv->bus;
> > +	const struct bus_type *bus = drv->bus;
> >   	struct device *dev;
> >   	int rc = -ENODEV;
> > @@ -32,7 +32,7 @@ static DRIVER_ATTR_IGNORE_LOCKDEP(unbind, 0200, NULL, unbind_store);
> >   static ssize_t bind_store(struct device_driver *drv, const char *buf, size_t count)
> >   {
> > -	struct bus_type *bus = drv->bus;
> > +	const struct bus_type *bus = drv->bus;
> >   	struct device *dev;
> >   	struct device_driver *alt_drv = NULL;
> >   	int rc = -ENODEV;
> 
> After applying this patch, warning is reported:
> 
> drivers/dma/idxd/compat.c: In function ‘bind_store’:
> drivers/dma/idxd/compat.c:47:47: warning: passing argument 2 of
> ‘driver_find’ discards ‘const’ qualifier from pointer target type
> [-Wdiscarded-qualifiers]
>    47 |                 alt_drv = driver_find("idxd", bus);
>       |                                               ^~~
> In file included from ./include/linux/device.h:32,
>                  from drivers/dma/idxd/compat.c:6:
> ./include/linux/device/driver.h:129:59: note: expected ‘struct bus_type *’
> but argument is of type ‘const struct bus_type *’
>   129 |                                          struct bus_type *bus);
>       |                                          ~~~~~~~~~~~~~~~~~^~~
> 
> Should the "bus" parameter in driver_find() definition be changed to const
> as well to avoid the warning?

Oops, yes, it needs an earlier patch in this series, sorry, I didn't
call that out properly in the notes section of the patch.

So I can just take this through my tree if that's ok.

thanks,

greg k-h

  reply	other threads:[~2023-03-16 10:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230313182918.1312597-1-gregkh@linuxfoundation.org>
2023-03-13 18:29 ` [PATCH 32/36] dmaengine: idxd: use const struct bus_type * Greg Kroah-Hartman
2023-03-13 19:07   ` Fenghua Yu
2023-03-16 10:16     ` Greg Kroah-Hartman [this message]
2023-03-16 23:57       ` Fenghua Yu
2023-03-24  8:57         ` Greg Kroah-Hartman
2023-03-17 17:19   ` Vinod Koul
2023-03-17 17:33   ` Dave Jiang

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=ZBLsYNXXCBkb8QlO@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=dave.jiang@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=fenghua.yu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=vkoul@kernel.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;
as well as URLs for NNTP newsgroup(s).