From: Jonathan Cameron <jic23@kernel.org>
To: Chris Ruehl <chris.ruehl@gtsys.com.hk>
Cc: devicetree@vger.kernel.org,
"Michael Hennerich" <michael.hennerich@analog.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Hartmut Knaack" <knaack.h@gmx.de>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Peter Meerwald-Stadler" <pmeerw@pmeerw.net>,
"Alexios Zavras" <alexios.zavras@intel.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/3] iio: documentation ltc2632_chip_info add num_channels
Date: Sat, 25 Apr 2020 20:37:23 +0100 [thread overview]
Message-ID: <20200425203723.01168c53@archlinux> (raw)
In-Reply-To: <20200420042612.27752-2-chris.ruehl@gtsys.com.hk>
On Mon, 20 Apr 2020 12:26:06 +0800
Chris Ruehl <chris.ruehl@gtsys.com.hk> wrote:
> The documentation for ltc_2632_chip_info missed the desciption for the
> num_channels. This trivial patch adds it.
>
> Signed-off-by: Chris Ruehl <chris.ruehl@gtsys.com.hk>
>
> Fixes: 9f15a4a0adc9 ("iio: dac: ltc2632: add support for LTC2636 family")
> Acked-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Might as well take this one as it stands on its own.
Applied to the togreg branch of iio.git and pushed out as testing for
the autobuilders to play with it.
Jonathan
> ---
> v5:
> tags added
>
> v4:
> Fix commit text.
> drivers/iio/dac/ltc2632.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/iio/dac/ltc2632.c b/drivers/iio/dac/ltc2632.c
> index 7adc91056aa1..2a84ea654645 100644
> --- a/drivers/iio/dac/ltc2632.c
> +++ b/drivers/iio/dac/ltc2632.c
> @@ -24,6 +24,7 @@
> /**
> * struct ltc2632_chip_info - chip specific information
> * @channels: channel spec for the DAC
> + * @num_channels: DAC channel count of the chip
> * @vref_mv: internal reference voltage
> */
> struct ltc2632_chip_info {
next prev parent reply other threads:[~2020-04-25 19:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 4:26 [PATCH v5] iio: patch set ltc2632 Chris Ruehl
2020-04-20 4:26 ` [PATCH v5 1/3] iio: documentation ltc2632_chip_info add num_channels Chris Ruehl
2020-04-25 19:37 ` Jonathan Cameron [this message]
2020-04-20 4:26 ` [PATCH v5 2/3] iio: DAC extension for ltc2634-12/10/8 Chris Ruehl
2020-04-30 15:17 ` Rob Herring
2020-04-20 4:26 ` [PATCH v5 3/3] iio/dac: convert ltc2632.txt to lltc,ltc2632.yaml Chris Ruehl
2020-04-25 19:35 ` Jonathan Cameron
2020-04-27 1:09 ` Chris Ruehl
2020-04-30 15:24 ` Rob Herring
2020-08-10 3:01 ` Chris Ruehl
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=20200425203723.01168c53@archlinux \
--to=jic23@kernel.org \
--cc=alexios.zavras@intel.com \
--cc=chris.ruehl@gtsys.com.hk \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.hennerich@analog.com \
--cc=pmeerw@pmeerw.net \
--cc=tglx@linutronix.de \
--cc=u.kleine-koenig@pengutronix.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;
as well as URLs for NNTP newsgroup(s).