linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PATCH 38/38] iio: drop iio_info.driver_module and iio_trigger_ops.owner.
Date: Sat, 24 Jun 2017 21:57:42 +0100	[thread overview]
Message-ID: <20170624215742.1bbb516d@kernel.org> (raw)
In-Reply-To: <87aa917c-8e89-83f5-0ca4-ca8bb40e9b18@metafoo.de>

On Mon, 12 Jun 2017 18:16:56 +0200
Lars-Peter Clausen <lars@metafoo.de> wrote:

> On 05/29/2017 05:51 PM, Jonathan Cameron wrote:
> > diff --git a/include/linux/iio/trigger.h b/include/linux/iio/trigger.h
> > index 2e1800ad265b..ff2b7c7a9652 100644
> > --- a/include/linux/iio/trigger.h
> > +++ b/include/linux/iio/trigger.h
> > @@ -34,7 +34,6 @@ struct iio_trigger;  
> 
> Update to the kernel-doc is missing here.
Just so I don't forget.  This patch also needs to remove the
bit of code that insists there is an iio_trigger_ops so that
the owner field can be read.

Will do a new version, perhaps tomorrow.

Thanks,

Jonathan
> 
> >   * instances of a given device.
> >   **/
> >  struct iio_trigger_ops {
> > -	struct module *owner;
> >  	int (*set_trigger_state)(struct iio_trigger *trig, bool state);
> >  	int (*try_reenable)(struct iio_trigger *trig);
> >  	int (*validate_device)(struct iio_trigger *trig,
> >  
> 


      reply	other threads:[~2017-06-24 20:57 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-29 15:51 [PATCH 00/38] IIO: Drop manual assignment of THIS_MODULE Jonathan Cameron
2017-05-29 15:51 ` [PATCH 01/38] iio: Use macro magic to avoid manual assign of driver_module Jonathan Cameron
2017-06-03  8:37   ` Jonathan Cameron
2017-06-12 16:13   ` Lars-Peter Clausen
2017-05-29 15:51 ` [PATCH 02/38] iio: triggers: Use macros to avoid boilerplate assignment of owner Jonathan Cameron
2017-05-29 15:51 ` [PATCH 03/38] coccinelle: Add an iio_no_owner semantic patch to drop driver_owner Jonathan Cameron
2017-05-29 15:51 ` [PATCH 04/38] iio:adc: drop assign iio_info.driver_module and iio_trigger_ops.owner Jonathan Cameron
2017-05-29 15:51 ` [PATCH 05/38] iio:accel: " Jonathan Cameron
2017-05-29 15:51 ` [PATCH 06/38] iio:amplifiers:ad8366 " Jonathan Cameron
2017-05-29 15:51 ` [PATCH 07/38] iio:chemical: " Jonathan Cameron
2017-05-29 15:51 ` [PATCH 08/38] iio:common: " Jonathan Cameron
2017-05-29 15:51 ` [PATCH 09/38] iio:counter:104-quad-8 drop assign iio_info.driver_module Jonathan Cameron
2017-05-29 15:51 ` [PATCH 10/38] iio:dac: drop assignment of iio_info.driver_module Jonathan Cameron
2017-05-29 15:51 ` [PATCH 11/38] iio:dummy: " Jonathan Cameron
2017-05-29 15:51 ` [PATCH 12/38] iio:frequency: drop assign iio_info.driver_module Jonathan Cameron
2017-05-29 15:51 ` [PATCH 13/38] iio:gyro: drop assign iio_info.driver_module and iio_trigger_ops.owner Jonathan Cameron
2017-05-29 15:51 ` [PATCH 14/38] iio:health: " Jonathan Cameron
2017-05-29 15:51 ` [PATCH 15/38] iio:humidity: " Jonathan Cameron
2017-05-29 15:51 ` [PATCH 16/38] iio:imu: " Jonathan Cameron
2017-05-29 15:51 ` [PATCH 17/38] iio:light: " Jonathan Cameron
2017-05-29 15:51 ` [PATCH 18/38] iio:magnetometer: " Jonathan Cameron
2017-05-29 15:51 ` [PATCH 19/38] iio:orientation: drop assign iio_info.driver_module Jonathan Cameron
2017-05-29 15:51 ` [PATCH 20/38] iio:dpot: " Jonathan Cameron
2017-05-29 15:51 ` [PATCH 21/38] iio:potentiostat:lmp91000 drop assign iio_info.driver_module and iio_trigger_ops.owner Jonathan Cameron
2017-05-29 15:51 ` [PATCH 22/38] iio:pressure: " Jonathan Cameron
2017-05-29 15:51 ` [PATCH 23/38] iio:proximity: " Jonathan Cameron
2017-05-29 15:51 ` [PATCH 24/38] iio:temperature: drop assignment of iio_info.driver_module Jonathan Cameron
2017-05-29 15:51 ` [PATCH 25/38] iio:triggers: drop assign iio_info.driver_module and iio_trigger_ops.owner Jonathan Cameron
2017-05-29 15:51 ` [PATCH 26/38] staging:iio:accel: drop assignment of iio_info.driver_module Jonathan Cameron
2017-05-29 15:51 ` [PATCH 27/38] staging:iio:adc: drop assign iio_info.driver_module Jonathan Cameron
2017-05-29 15:51 ` [PATCH 28/38] staging:iio:cdc: " Jonathan Cameron
2017-05-29 15:51 ` [PATCH 29/38] staging:iio:frequency: " Jonathan Cameron
2017-05-29 15:51 ` [PATCH 30/38] staging:iio:gyro:adis16060 " Jonathan Cameron
2017-05-29 15:51 ` [PATCH 31/38] staging:iio:ad5933: " Jonathan Cameron
2017-05-29 15:51 ` [PATCH 32/38] staging:iio:meter: drop assign iio_info.driver_module and iio_trigger_ops.owner Jonathan Cameron
2017-05-29 15:51 ` [PATCH 33/38] iio:resolver: drop assignment of iio_info.driver_module Jonathan Cameron
2017-05-29 15:51 ` [PATCH 34/38] iio:adc: drop assignment of iio_trigger_ops.owner Jonathan Cameron
2017-05-29 15:51 ` [PATCH 35/38] staging:iio:light:tsl2x7x drop assignment of driver_module Jonathan Cameron
2017-05-29 15:51 ` [PATCH 36/38] input: tsc2007 - drop the driver_module assignment in iio interface Jonathan Cameron
2017-05-30  2:41   ` Dmitry Torokhov
2017-05-29 15:51 ` [PATCH 37/38] platform/x86: toshiba_acpi: drop assignment of iio_info.driver_module Jonathan Cameron
2017-05-29 17:56   ` Andy Shevchenko
2017-06-07 14:53   ` Azael Avalos
2017-06-11 14:03     ` Jonathan Cameron
2017-05-29 15:51 ` [PATCH 38/38] iio: drop iio_info.driver_module and iio_trigger_ops.owner Jonathan Cameron
2017-06-12 16:16   ` Lars-Peter Clausen
2017-06-24 20:57     ` Jonathan Cameron [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=20170624215742.1bbb516d@kernel.org \
    --to=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.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).