From: Marcelo Schmitt <marcelo.schmitt1@gmail.com>
To: lars@metafoo.de, Michael.Hennerich@analog.com, jic23@kernel.org,
knaack.h@gmx.de, pmeerw@pmeerw.net
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-usp@googlegroups.com
Subject: [PATCH v3 0/7] move out of staging
Date: Sun, 10 Mar 2019 14:44:34 -0300 [thread overview]
Message-ID: <20190310174434.7t73fdbqbqezh3z6@smtp.gmail.com> (raw)
This series of patches make code style adjusts on comments and include
order.
It adds a SPDX license identifier of GPL-2.0.
It makes Kconfig help message more compact and correct.
It adds an ABI documentation for the device attributes.
It changes device attributes to use more suitable ABI functions.
Finally, it moves the ad5933 driver from staging directory to iio main
drivers directory.
Marcelo Schmitt (7):
staging: iio: ad5933: change multi-line comment style
staging: iio: ad5933: organize includes
staging: iio: ad5933: add SPDX identifier
staging: iio: ad5933: change help rule message
staging: iio: ad5933: add ABI documentation
staging: iio: ad5933: change attributes' ABI call
staging: iio: ad5933: move out of staging
.../ABI/testing/sysfs-bus-iio-ad5933 | 39 +
drivers/iio/impedance-analyzer/Kconfig | 18 +
drivers/iio/impedance-analyzer/Makefile | 5 +
drivers/iio/impedance-analyzer/ad5933.c | 811 ++++++++++++++++++
.../staging/iio/impedance-analyzer/Kconfig | 18 -
.../staging/iio/impedance-analyzer/Makefile | 5 -
.../staging/iio/impedance-analyzer/ad5933.c | 809 -----------------
7 files changed, 873 insertions(+), 832 deletions(-)
create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-ad5933
create mode 100644 drivers/iio/impedance-analyzer/Kconfig
create mode 100644 drivers/iio/impedance-analyzer/Makefile
create mode 100644 drivers/iio/impedance-analyzer/ad5933.c
delete mode 100644 drivers/staging/iio/impedance-analyzer/Kconfig
delete mode 100644 drivers/staging/iio/impedance-analyzer/Makefile
delete mode 100644 drivers/staging/iio/impedance-analyzer/ad5933.c
--
2.20.1
reply other threads:[~2019-03-10 17:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190310174434.7t73fdbqbqezh3z6@smtp.gmail.com \
--to=marcelo.schmitt1@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=jic23@kernel.org \
--cc=kernel-usp@googlegroups.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).