From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: linux-acpi@vger.kernel.org, linux-i2c@vger.kernel.org,
netdev@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Wolfram Sang <wsa@kernel.org>
Subject: Re: [PATCH RFC 1/2] i2c: add fwnode APIs
Date: Mon, 19 Dec 2022 08:47:07 +0000 [thread overview]
Message-ID: <Y6AlC+9iGVGzWSbc@shell.armlinux.org.uk> (raw)
In-Reply-To: <Y5G5ZyO1XRgjfN90@shell.armlinux.org.uk>
Hi Mika,
On Thu, Dec 08, 2022 at 10:16:07AM +0000, Russell King (Oracle) wrote:
> Hi Mika,
>
> On Thu, Dec 08, 2022 at 12:04:02PM +0200, Mika Westerberg wrote:
> > Hi,
> >
> > On Wed, Dec 07, 2022 at 11:22:24AM +0000, Russell King (Oracle) wrote:
> > > +EXPORT_SYMBOL(i2c_find_device_by_fwnode);
> > > +
> >
> > Drop this empty line.
>
> The additional empty line was there before, and I guess is something the
> I2C maintainer wants to logically separate the i2c device stuff from
> the rest of the file.
>
> > > +/* must call put_device() when done with returned i2c_client device */
> > > +struct i2c_client *i2c_find_device_by_fwnode(struct fwnode_handle *fwnode);
> >
> > With the kernel-docs in place you probably can drop these comments.
>
> It's what is there against the other prototypes - and is very easy to
> get wrong, as I've recently noticed in the sfp.c code as a result of
> creating this series.
>
> I find the whole _find_ vs _get_ thing a tad confusing, and there
> probably should be just one interface with one way of putting
> afterwards to avoid subtle long-standing bugs like this.
>
> Thanks.
Do you have any comments on my reply please?
Thanks.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2022-12-19 8:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 11:21 [PATCH RFC 0/2] Add I2C fwnode lookup/get interfaces Russell King (Oracle)
2022-12-07 11:22 ` [PATCH RFC 1/2] i2c: add fwnode APIs Russell King (Oracle)
2022-12-08 10:04 ` Mika Westerberg
2022-12-08 10:16 ` Russell King (Oracle)
2022-12-19 8:47 ` Russell King (Oracle) [this message]
2022-12-19 9:23 ` Mika Westerberg
2022-12-07 11:22 ` [PATCH RFC 2/2] net: sfp: use i2c_get_adapter_by_fwnode() Russell King (Oracle)
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=Y6AlC+9iGVGzWSbc@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=wsa@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).