From: William Breathitt Gray <vilhelm.gray@gmail.com>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Jonathan Cameron <jic23@kernel.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Matt Ranostay <matt.ranostay@konsulko.com>,
linux-iio@vger.kernel.org
Subject: Re: [PATCH 1/8] iio: stx104: Set parent device
Date: Sat, 11 Feb 2017 07:58:33 -0500 [thread overview]
Message-ID: <20170211125833.GA31343@sophia> (raw)
In-Reply-To: <1486816461-28618-2-git-send-email-lars@metafoo.de>
On Sat, Feb 11, 2017 at 01:34:14PM +0100, Lars-Peter Clausen wrote:
>Initialize the parent of the IIO device to the device that registered it.
>This makes sure that the IIO device appears the right level in the device
>hierarchy.
>
>Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
>---
> drivers/iio/adc/stx104.c | 1 +
> 1 file changed, 1 insertion(+)
>
>diff --git a/drivers/iio/adc/stx104.c b/drivers/iio/adc/stx104.c
>index be2de48..2df84fa5 100644
>--- a/drivers/iio/adc/stx104.c
>+++ b/drivers/iio/adc/stx104.c
>@@ -318,6 +318,7 @@ static int stx104_probe(struct device *dev, unsigned int id)
> }
>
> indio_dev->name = dev_name(dev);
>+ indio_dev->dev.parent = dev;
>
> priv = iio_priv(indio_dev);
> priv->base = base[id];
>--
>2.1.4
>
Acked-by: William Breathitt Gray <vilhelm.gray@gmail.com
next prev parent reply other threads:[~2017-02-11 12:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-11 12:34 [PATCH 0/8] iio: Fix missing parent device initalization Lars-Peter Clausen
2017-02-11 12:34 ` [PATCH 1/8] iio: stx104: Set parent device Lars-Peter Clausen
2017-02-11 12:58 ` William Breathitt Gray [this message]
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=20170211125833.GA31343@sophia \
--to=vilhelm.gray@gmail.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=matt.ranostay@konsulko.com \
--cc=pmeerw@pmeerw.net \
/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).