From: Jonathan Cameron <jic23@kernel.org>
To: linux-iio@vger.kernel.org
Cc: jbrenner@TAOSinc.com, Jonathan Cameron <jic23@kernel.org>
Subject: [PATCH 4/4] staging:iio: chan_spec - take extend_name constant.
Date: Tue, 10 Apr 2012 21:17:32 +0100 [thread overview]
Message-ID: <1334089052-22304-5-git-send-email-jic23@kernel.org> (raw)
In-Reply-To: <1334089052-22304-1-git-send-email-jic23@kernel.org>
I can't envision a case where this is not constant and we
don't seem to have any in tree, so lets clear up this loose
end.
Signed-off-by: Jonathan Cameron <jic23@kernel.org>
---
drivers/staging/iio/iio.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/iio/iio.h b/drivers/staging/iio/iio.h
index 833a849..4824812 100644
--- a/drivers/staging/iio/iio.h
+++ b/drivers/staging/iio/iio.h
@@ -164,7 +164,7 @@ struct iio_chan_spec {
long info_mask;
long event_mask;
const struct iio_chan_spec_ext_info *ext_info;
- char *extend_name;
+ const char *extend_name;
const char *datasheet_name;
unsigned processed_val:1;
unsigned modified:1;
--
1.7.9.4
next prev parent reply other threads:[~2012-04-10 20:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 20:17 [PATCH 0/4] IIO: Another set of buglets plus cleanups Jonathan Cameron
2012-04-10 20:17 ` [PATCH 1/4] staging:iio:light:tsl2563 channel spec buglet / always reading same adc Jonathan Cameron
2012-04-10 20:17 ` [PATCH 2/4] staging:iio:Documentation: Fix a cut and paste error Jonathan Cameron
2012-04-11 8:19 ` Maxime Ripard
2012-04-11 8:20 ` Jonathan Cameron
2012-04-10 20:17 ` [PATCH 3/4] staging:iio:iio_core.h make less dependent on other included headers Jonathan Cameron
2012-04-10 20:17 ` Jonathan Cameron [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-04-13 9:24 [PATCH 0/4] IIO: Another set of buglets plus cleanups Jonathan Cameron
2012-04-13 9:24 ` [PATCH 4/4] staging:iio: chan_spec - take extend_name constant 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=1334089052-22304-5-git-send-email-jic23@kernel.org \
--to=jic23@kernel.org \
--cc=jbrenner@TAOSinc.com \
--cc=linux-iio@vger.kernel.org \
/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).