From: Alex Frappier Lachapelle <alex.frappierlachapelle@gmail.com>
To: greg@kroah.com
Cc: abbotti@mev.co.uk, hsweeten@visionengravers.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Alex Frappier Lachapelle <Alex.FrappierLachapelle@gmail.com>
Subject: [PATCH] Staging: comedi: das16: Fixed a const struct coding style issue
Date: Sat, 25 Nov 2017 20:50:25 -0500 [thread overview]
Message-ID: <20171126015025.11575-1-Alex.FrappierLachapelle@gmail.com> (raw)
Fixed a coding style issue.
Signed-off-by: Alex Frappier Lachapelle <Alex.FrappierLachapelle@gmail.com>
---
drivers/staging/comedi/drivers/das16.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/comedi/drivers/das16.c b/drivers/staging/comedi/drivers/das16.c
index ddd4aeab6365..ed1e9e9b651d 100644
--- a/drivers/staging/comedi/drivers/das16.c
+++ b/drivers/staging/comedi/drivers/das16.c
@@ -967,7 +967,7 @@ static const struct comedi_lrange *das16_ai_range(struct comedi_device *dev,
/* get any user-defined input range */
if (pg_type == das16_pg_none && (min || max)) {
- struct comedi_lrange *lrange;
+ const struct comedi_lrange *lrange;
struct comedi_krange *krange;
/* allocate single-range range table */
@@ -1001,7 +1001,7 @@ static const struct comedi_lrange *das16_ao_range(struct comedi_device *dev,
/* get any user-defined output range */
if (min || max) {
- struct comedi_lrange *lrange;
+ const struct comedi_lrange *lrange;
struct comedi_krange *krange;
/* allocate single-range range table */
--
2.15.0
next reply other threads:[~2017-11-26 1:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-26 1:50 Alex Frappier Lachapelle [this message]
2017-11-27 10:28 ` Ian Abbott
2017-11-27 17:51 ` Hartley Sweeten
2017-11-27 22:36 ` Dan Carpenter
2017-11-28 6:59 ` greg
2017-11-28 2:37 ` kbuild test robot
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=20171126015025.11575-1-Alex.FrappierLachapelle@gmail.com \
--to=alex.frappierlachapelle@gmail.com \
--cc=abbotti@mev.co.uk \
--cc=devel@driverdev.osuosl.org \
--cc=greg@kroah.com \
--cc=hsweeten@visionengravers.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®