From: Nicholas Mc Guire <der.herr@hofr.at>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
Nicholas Mc Guire <hofrat@osadl.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-i2c <linux-i2c@vger.kernel.org>,
Linux Documentation List <linux-doc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Documentation: i2c: drop unnecessary .owner field in examples
Date: Sat, 3 Feb 2018 15:11:25 +0000 [thread overview]
Message-ID: <20180203151125.GA17486@osadl.at> (raw)
In-Reply-To: <20180115202847.77s42fgc2zsdnc6s@ninjato>
On Mon, Jan 15, 2018 at 09:28:47PM +0100, Wolfram Sang wrote:
> On Mon, Jan 15, 2018 at 10:24:52PM +0200, Andy Shevchenko wrote:
> > On Mon, Jan 15, 2018 at 2:08 PM, Nicholas Mc Guire <hofrat@osadl.org> wrote:
> > > From: Nicholas Mc Guire <hofrat@osadl.at>
> > >
> > > Currently there are a few drivers that still set the .owner
> > > in the i2c_driver structure - all of which are reported by
> > > coccinelle (scripts/coccinelle/api/platform_no_drv_owner.cocci)
> > > and there are no cases that set the .onwer and do not call any
> > > of the functions that set the .owner field anyway in any of the
> > > drivers (checked by a modified coccinelle script based on the
> > > above) so it seems that the examples are no longer valid and
> > > .owner = THIS_MODULE, can be removed here.
> > >
> > > While at it an obvious typo (new new) was also fixed.
> >
> > AFAIU It is right only in case when someone does this, e.g.
> > module_i2c_driver() macro. Otherwise the field is pretty valid and
> > must be filled.
>
> It gets filled with i2c_add_driver. module_i2c_driver uses
> i2c_add_driver. I was about to suggest to keep the field in the old
> driver and describe that it can be removed when using one of
> i2c_add_driver or module_i2c_driver.
>
> But then I realised that the kernel tree does not have any such old
> drivers anymore and I couldn't even find out-of-tree code via some
> search engines (I tried looking for "I2C_CLIENT_INSMOD").
>
> I consider this obsolete and irrelevant these days. It might be good to
> simply remove it to not confuse users.
>
Not sure what the status of this is now - but I would
want to clean up some of the coccinelle findings - as a pre-requisite
it would make sense to either drop the examples inclusion of
.owner = THIS_MODULE or add a note in the documentation making
clear that this is only needed in case where the appropriate
module initialization helpers are not used. Is there any good
reason *not* to use these initialization helpers when upgrading
a driver ? If not (and I could not find one) then it might simply
be the right way to recommend using the initialization helpers and
drop the .owner = THIS_MODULE from the examples.
Anyway - cleaning up coccinelle findings would seem futile if the
documentation may be the cause.
thx!
hofrat
prev parent reply other threads:[~2018-02-03 15:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 12:08 [PATCH] Documentation: i2c: drop unnecessary .owner field in examples Nicholas Mc Guire
2018-01-15 20:24 ` Andy Shevchenko
2018-01-15 20:28 ` Wolfram Sang
2018-02-03 15:11 ` Nicholas Mc Guire [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=20180203151125.GA17486@osadl.at \
--to=der.herr@hofr.at \
--cc=andy.shevchenko@gmail.com \
--cc=corbet@lwn.net \
--cc=hofrat@osadl.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa@the-dreams.de \
/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