All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Silesh C V <svellattu@mvista.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Driver core: add bus_find_device_by_fwnode
Date: Mon, 24 Sep 2018 09:04:53 +0200	[thread overview]
Message-ID: <20180924070453.GA7105@kroah.com> (raw)
In-Reply-To: <CALabi0Ho9w_6PcSe6D8PmGgLfw9sYWhBS-z=KebxCPqkaM8ibw@mail.gmail.com>

On Mon, Sep 24, 2018 at 12:06:13PM +0530, Silesh C V wrote:
> Hello Greg,
> On Mon, Sep 24, 2018 at 10:48 AM Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > On Mon, Sep 24, 2018 at 10:05:55AM +0530, Silesh C V wrote:
> > > Some drivers need to find the device on a bus having a specific firmware
> > > node. Currently, such drivers have their own implementations to do this.
> > > Provide a helper similar to bus_find_device_by_name so that each driver
> > > does not have to reinvent this.
> >
> > Is there a second patch that uses this function?  We don't add api calls
> > that are not used.
> 
> OK. If I change, say, of_find_i2c_device_by_node,
> of_find_i2c_adapter_by_node, of_phy_find_device and
> of_find_spi_device_by_node to use this API, will that be good enough?
> If that is OK, I will send this as a series in v2.

I have no idea.  Why would you want to create a new api call with no
users?  Let's see the patch series before being able to properly judge
it...

thanks,

greg k-h

      reply	other threads:[~2018-09-24  7:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-24  4:35 [PATCH] Driver core: add bus_find_device_by_fwnode Silesh C V
2018-09-24  5:18 ` Greg Kroah-Hartman
2018-09-24  6:36   ` Silesh C V
2018-09-24  7:04     ` Greg Kroah-Hartman [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=20180924070453.GA7105@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=svellattu@mvista.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 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.