From: Himanshi Jain <himshijain.hj@gmail.com>
To: outreachy-kernel@googlegroups.com, lars@metafoo.de,
Michael.Hennerich@analog.com, jic23@kernel.org, knaack.h@gmx.de,
pmeerw@pmeerw.net, gregkh@linuxfoundation.org,
linux-iio@vger.kernel.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, nick.desaulniers@gmail.com,
daniel.baluta@gmail.com
Subject: [PATCH v2 0/2] Rewrite the IIO_DEVICE_ATTR_NAMED API to pass name as string.
Date: Wed, 13 Sep 2017 14:25:02 +0530 [thread overview]
Message-ID: <cover.1505291907.git.himshijain.hj@gmail.com> (raw)
This patchset is to rewrite the IIO_DEVICE_ATTR_NAMED API to pass name
as string.
Change in v2:
Split patch into two based on subsytems affected.
Himanshi Jain (2):
include: linux: sysfs: Add __ATTR_NAMED macro
iio: Change to __ATTR_NAMED()
drivers/iio/adc/ad7793.c | 2 +-
drivers/staging/iio/adc/ad7192.c | 2 +-
drivers/staging/iio/adc/ad7280a.c | 4 ++--
include/linux/iio/sysfs.h | 6 +++++-
include/linux/sysfs.h | 7 +++++++
5 files changed, 16 insertions(+), 5 deletions(-)
--
1.9.1
next reply other threads:[~2017-09-13 8:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-13 8:55 Himanshi Jain [this message]
2017-09-13 8:44 ` [PATCH v2 1/2] include: linux: sysfs: Add __ATTR_NAMED macro Himanshi Jain
2017-09-13 8:44 ` [PATCH v2 2/2] iio: Change to __ATTR_NAMED() Himanshi Jain
2017-09-13 17:03 ` [PATCH v2 1/2] include: linux: sysfs: Add __ATTR_NAMED macro Jonathan Cameron
2017-09-13 18:58 ` Greg KH
2017-09-13 19:23 ` Lars-Peter Clausen
2017-09-13 20:50 ` Jonathan Cameron
2017-09-18 10:49 ` Himanshi Jain
2017-09-21 13:54 ` Jonathan Cameron
2017-09-21 14:07 ` [Outreachy kernel] " Julia Lawall
2017-09-13 21:29 ` Greg KH
2017-09-13 21:43 ` Dan Carpenter
2017-09-13 21:58 ` Joe Perches
2017-09-13 23:16 ` Jonathan Cameron
2017-09-14 5:10 ` [Outreachy kernel] " Julia Lawall
2017-09-19 12:13 ` Lars-Peter Clausen
2017-09-13 8:46 ` [Outreachy kernel] [PATCH v2 0/2] Rewrite the IIO_DEVICE_ATTR_NAMED API to pass name as string Julia Lawall
2017-09-13 17: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=cover.1505291907.git.himshijain.hj@gmail.com \
--to=himshijain.hj@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=daniel.baluta@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.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=nick.desaulniers@gmail.com \
--cc=outreachy-kernel@googlegroups.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).