From: Chris Ruehl <chris.ruehl@gtsys.com.hk>
To: Chris Ruehl <chris.ruehl@gtsys.com.hk>
Cc: devicetree@vger.kernel.org,
"Michael Hennerich" <michael.hennerich@analog.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"Hartmut Knaack" <knaack.h@gmx.de>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Peter Meerwald-Stadler" <pmeerw@pmeerw.net>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Richard Fontana" <rfontana@redhat.com>,
"Alexios Zavras" <alexios.zavras@intel.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v5] iio: patch set ltc2632
Date: Mon, 20 Apr 2020 12:26:05 +0800 [thread overview]
Message-ID: <20200420042612.27752-1-chris.ruehl@gtsys.com.hk> (raw)
Patchset to extend ltc2632 spi driver to support the similar chip set
ltc2634.
* Patch v2 1/3 update documentation struct ltc2632_chip_info
* Patch v2 2/3 patch ltc2632.c,Kconfig,ltc2632.txt(devtree)
* Patch v2 3/3 convert ltc2632.txt to yaml format named lltc,ltc2632.yaml
* Patch v3 2/3 : correct help text
* Patch v4 1/3 : correct spelling in commit
*/3 hide change history below ---
* Patch v5 : 1/3,2/3 add Accept-by and fixed tag,
3/3 maintainer & correct required seciton
Signed-off-by: Chris Ruehl <chris.ruehl@gtsys.com.hk>
---
next reply other threads:[~2020-04-20 4:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 4:26 Chris Ruehl [this message]
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
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=20200420042612.27752-1-chris.ruehl@gtsys.com.hk \
--to=chris.ruehl@gtsys.com.hk \
--cc=alexios.zavras@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.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=rfontana@redhat.com \
--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).