linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Hartmut Knaack <knaack.h@gmx.de>,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
	William Breathitt Gray <vilhelm.gray@gmail.com>,
	Matt Ranostay <matt.ranostay@konsulko.com>,
	linux-iio@vger.kernel.org, Lars-Peter Clausen <lars@metafoo.de>
Subject: [PATCH 0/8] iio: Fix missing parent device initalization
Date: Sat, 11 Feb 2017 13:34:13 +0100	[thread overview]
Message-ID: <1486816461-28618-1-git-send-email-lars@metafoo.de> (raw)

Add parent device initialization to drivers that are currently missing it.
Setting the parent device makes sure that the IIO device shows up at the
right level in the device hierachy.

The following coccinelle semantic patch was used to find the offending
drivers:
// <smpl>
@r1@
identifier indio_dev;
position p;
@@
indio_dev->dev.parent = ...;
...
(
iio_device_register@p(indio_dev)
|
devm_iio_device_register@p(..., indio_dev)
)

@@
position p != r1.p;
identifier indio_dev;
@@
(
*iio_device_register@p(indio_dev)
|
*devm_iio_device_register@p(..., indio_dev)
)
// </smpl>

- Lars

Lars-Peter Clausen (8):
  iio: stx104: Set parent device
  iio: quad-8: Set parent device
  iio: cio-dac: Set parent device
  iio: max30100: Set parent device
  iio: max30102: Set parent device
  iio: lmp91000: Set parent device
  iio: pulsedlight-lidar-lite-v2: Set parent device
  iio: maxim_thermocouple: Set parent device

 drivers/iio/adc/stx104.c                          | 1 +
 drivers/iio/counter/104-quad-8.c                  | 1 +
 drivers/iio/dac/cio-dac.c                         | 1 +
 drivers/iio/health/max30100.c                     | 1 +
 drivers/iio/health/max30102.c                     | 1 +
 drivers/iio/potentiostat/lmp91000.c               | 1 +
 drivers/iio/proximity/pulsedlight-lidar-lite-v2.c | 1 +
 drivers/iio/temperature/maxim_thermocouple.c      | 1 +
 8 files changed, 8 insertions(+)

-- 
2.1.4

             reply	other threads:[~2017-02-11 12:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-11 12:34 Lars-Peter Clausen [this message]
2017-02-11 12:34 ` [PATCH 1/8] iio: stx104: Set parent device Lars-Peter Clausen
2017-02-11 12:58   ` William Breathitt Gray
2017-02-19 11:55     ` Jonathan Cameron
2017-02-11 12:34 ` [PATCH 2/8] iio: quad-8: " Lars-Peter Clausen
2017-02-11 12:59   ` William Breathitt Gray
2017-02-11 12:34 ` [PATCH 3/8] iio: cio-dac: " Lars-Peter Clausen
2017-02-11 12:59   ` William Breathitt Gray
2017-02-19 11:58     ` Jonathan Cameron
2017-02-11 12:34 ` [PATCH 4/8] iio: max30100: " Lars-Peter Clausen
2017-02-19 12:00   ` Jonathan Cameron
2017-02-11 12:34 ` [PATCH 5/8] iio: max30102: " Lars-Peter Clausen
2017-02-19 12:01   ` Jonathan Cameron
2017-02-11 12:34 ` [PATCH 6/8] iio: lmp91000: " Lars-Peter Clausen
2017-02-14 15:39   ` Matt Ranostay
2017-02-19 12:02     ` Jonathan Cameron
2017-02-11 12:34 ` [PATCH 7/8] iio: pulsedlight-lidar-lite-v2: " Lars-Peter Clausen
2017-02-14 15:40   ` Matt Ranostay
2017-02-19 12:02     ` Jonathan Cameron
2017-02-11 12:34 ` [PATCH 8/8] iio: maxim_thermocouple: " Lars-Peter Clausen
2017-02-19 12:04   ` Jonathan Cameron

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=1486816461-28618-1-git-send-email-lars@metafoo.de \
    --to=lars@metafoo.de \
    --cc=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=matt.ranostay@konsulko.com \
    --cc=pmeerw@pmeerw.net \
    --cc=vilhelm.gray@gmail.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).