From: Dan Carpenter <dan.carpenter@linaro.org>
To: Umang Jain <umang.jain@ideasonboard.com>
Cc: linux-staging@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-rpi-kernel@lists.infradead.org,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
Stefan Wahren <stefan.wahren@i2se.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Adrien Thierry <athierry@redhat.com>,
Dan Carpenter <error27@gmail.com>,
Dave Stevenson <dave.stevenson@raspberrypi.com>,
Kieran Bingham <kieran.bingham@ideasonboard.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: [PATCH v11 1/5] staging: vc04_services: vchiq_arm: Add new bus type and device type
Date: Mon, 25 Sep 2023 15:18:50 +0300 [thread overview]
Message-ID: <62363da5-39c4-40f2-bfca-fed182845eb8@kadam.mountain> (raw)
In-Reply-To: <700e11e4-057d-78ed-8b52-dd2df97198bf@ideasonboard.com>
On Sat, Sep 23, 2023 at 07:57:51PM +0530, Umang Jain wrote:
> Hi Dan,
>
> On 9/14/23 12:25 PM, Dan Carpenter wrote:
> > On Thu, Sep 14, 2023 at 01:23:50AM +0530, Umang Jain wrote:
> > > +static int vchiq_bus_type_match(struct device *dev, struct device_driver *drv)
> > > +{
> > > + if (dev->bus == &vchiq_bus_type &&
> > > + strcmp(dev_name(dev), drv->name) == 0)
> > > + return 1;
> > > +
> > > + return 0;
> > > +}
> > I was not going to comment on this, because it's unfair to nitpick a
> > v11 patch... But since you're going to have to redo it anyway, could
> > you make this function bool and change it to return true/false.
> >
> > static bool vchiq_bus_type_match(struct device *dev, struct device_driver *drv)
>
> Perhaps the return value can be true/false, but return type should always be
> 'int'
>
Oh. Sorry, I didn't look carefully.
Btw, you don't need to tip toe around telling me I'm wrong. Just say
"That won't compile, dummy." I'm a big boy, and I can admit when I make
mistakes. ;)
regards,
dan carpenter
next prev parent reply other threads:[~2023-09-25 12:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 19:53 [PATCH v11 0/5] staging: vc04_services: vchiq: Register devices with a custom bus_type Umang Jain
2023-09-13 19:53 ` [PATCH v11 1/5] staging: vc04_services: vchiq_arm: Add new bus type and device type Umang Jain
2023-09-13 20:58 ` Stefan Wahren
2023-09-14 22:15 ` Robin Murphy
2023-09-14 6:55 ` Dan Carpenter
[not found] ` <700e11e4-057d-78ed-8b52-dd2df97198bf@ideasonboard.com>
2023-09-25 12:18 ` Dan Carpenter [this message]
2023-09-17 8:40 ` Stefan Wahren
2023-09-13 19:53 ` [PATCH v11 2/5] staging: vc04_services: vchiq_arm: Register vchiq_bus_type Umang Jain
2023-09-13 21:01 ` Stefan Wahren
2023-09-14 8:22 ` Umang Jain
2023-09-13 19:53 ` [PATCH v11 3/5] staging: bcm2835-camera: Register bcm2835-camera with vchiq_bus_type Umang Jain
2023-09-13 19:53 ` [PATCH v11 4/5] staging: bcm2835-audio: Register bcm2835-audio " Umang Jain
2023-09-13 19:53 ` [PATCH v11 5/5] staging: vc04_services: vchiq_arm: Remove vchiq_register_child() Umang Jain
2023-09-14 6:45 ` Dan Carpenter
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=62363da5-39c4-40f2-bfca-fed182845eb8@kadam.mountain \
--to=dan.carpenter@linaro.org \
--cc=athierry@redhat.com \
--cc=dave.stevenson@raspberrypi.com \
--cc=error27@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kieran.bingham@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux-staging@lists.linux.dev \
--cc=stefan.wahren@i2se.com \
--cc=umang.jain@ideasonboard.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