From: Greg KH <gregkh@linuxfoundation.org>
To: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: linux-kernel@vger.kernel.org, rafael@kernel.org,
Alessandro Zummo <a.zummo@towertech.it>,
Alexander Aring <alex.aring@gmail.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Andrew Lunn <andrew@lunn.ch>, Arnd Bergmann <arnd@arndb.de>,
Dan Murphy <dmurphy@ti.com>,
"David S. Miller" <davem@davemloft.net>,
Florian Fainelli <f.fainelli@gmail.com>,
Harald Freudenberger <freude@linux.ibm.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
Jacek Anaszewski <jacek.anaszewski@gmail.com>,
Jiri Slaby <jslaby@suse.com>, Liam Girdwood <lgirdwood@gmail.com>,
linux-leds@vger.kernel.org, linux-rtc@vger.kernel.org,
linux-usb@vger.kernel.org, linux-wpan@vger.kernel.org,
Mark Brown <broonie@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Pavel Machek <pavel@ucw.cz>, Peter Rosin <peda@axentia.se>,
Stefan Schmidt <stefan@datenfreihafen.org>,
Tomas Winkler <tomas.winkler@intel.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: [PATCH 10/13] drivers: Introduce variants of class_find_device()
Date: Wed, 5 Jun 2019 18:14:39 +0200 [thread overview]
Message-ID: <20190605161439.GB17272@kroah.com> (raw)
In-Reply-To: <1559747630-28065-11-git-send-email-suzuki.poulose@arm.com>
On Wed, Jun 05, 2019 at 04:13:47PM +0100, Suzuki K Poulose wrote:
> +/**
> + * class_find_device_by_devt : device iterator for locating a particular device
> + * matching the device type.
> + * @class: class type
> + * @start: device to start search from
> + * @devt: device type of the device to match.
> + */
> +static inline struct device *class_find_device_by_devt(struct class *class,
> + struct device *start,
> + dev_t devt)
> +{
> + return class_find_device(class, start, &devt, device_match_devt);
> +}
Still has the start parameter, despite the changelog saying it would not
:(
next prev parent reply other threads:[~2019-06-05 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1559747630-28065-1-git-send-email-suzuki.poulose@arm.com>
2019-06-05 15:13 ` [PATCH 08/13] drivers: Add generic helper to match by name Suzuki K Poulose
2019-06-05 15:13 ` [PATCH 10/13] drivers: Introduce variants of class_find_device() Suzuki K Poulose
2019-06-05 16:14 ` Greg KH [this message]
2019-06-05 18:13 ` Suzuki K Poulose
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=20190605161439.GB17272@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=a.zummo@towertech.it \
--cc=alex.aring@gmail.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=davem@davemloft.net \
--cc=dmurphy@ti.com \
--cc=f.fainelli@gmail.com \
--cc=freude@linux.ibm.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=heiko.carstens@de.ibm.com \
--cc=hkallweit1@gmail.com \
--cc=jacek.anaszewski@gmail.com \
--cc=jslaby@suse.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=pavel@ucw.cz \
--cc=peda@axentia.se \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=stefan@datenfreihafen.org \
--cc=suzuki.poulose@arm.com \
--cc=tomas.winkler@intel.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;
as well as URLs for NNTP newsgroup(s).