From: Rodrigo Ribeiro <rodrigorsdc@gmail.com>
To: lars@metafoo.de, Michael.Hennerich@analog.com, jic23@kernel.org,
knaack.h@gmx.de, pmeerw@pmeerw.net, gregkh@linuxfoundation.org
Cc: linux-iio@vger.kernel.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, kernel-usp@googlegroups.com,
Rafael Tsuha <rafael.tsuha@usp.br>
Subject: [PATCH] staging:iio:ad7152: Rename misspelled RESEVERD -> RESERVED
Date: Thu, 24 Jan 2019 17:31:56 -0200 [thread overview]
Message-ID: <1548358316-8062-1-git-send-email-rodrigorsdc@gmail.com> (raw)
Remove the checkpatch.pl check:
CHECK: 'RESEVERD' may be misspelled - perhaps 'RESERVED'?
Signed-off-by: Rodrigo Ribeiro <rodrigorsdc@gmail.com>
Signed-off-by: Rafael Tsuha <rafael.tsuha@usp.br>
---
This macro is not used anywhere. Should we just correct the
spelling or remove the macro?
drivers/staging/iio/cdc/ad7152.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/iio/cdc/ad7152.c b/drivers/staging/iio/cdc/ad7152.c
index 25f51db..c9da6d4 100644
--- a/drivers/staging/iio/cdc/ad7152.c
+++ b/drivers/staging/iio/cdc/ad7152.c
@@ -35,7 +35,7 @@
#define AD7152_REG_CH2_GAIN_HIGH 12
#define AD7152_REG_CH2_SETUP 14
#define AD7152_REG_CFG 15
-#define AD7152_REG_RESEVERD 16
+#define AD7152_REG_RESERVED 16
#define AD7152_REG_CAPDAC_POS 17
#define AD7152_REG_CAPDAC_NEG 18
#define AD7152_REG_CFG2 26
--
2.7.4
next reply other threads:[~2019-01-24 19:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-24 19:31 Rodrigo Ribeiro [this message]
2019-01-25 8:19 ` [PATCH] staging:iio:ad7152: Rename misspelled RESEVERD -> RESERVED Alexandru Ardelean
2019-01-25 23:46 ` Rodrigo Ribeiro
2019-01-26 0:14 ` Rodrigo Ribeiro
2019-01-26 18:13 ` Jonathan Cameron
2019-01-29 9:10 ` Alexandru Ardelean
[not found] ` <CAOeBkLok_PJ-ZbHcTN-yc6+p-qb5RMMmALp4fOpfAr2cqRO5Ug@mail.gmail.com>
2019-02-14 10:51 ` Popa, Stefan Serban
2019-02-18 14:46 ` Jonathan Cameron
2019-02-18 17:00 ` Rodrigo Ribeiro
2019-02-20 15:20 ` Jonathan Cameron
2019-01-28 2:47 ` valdis.kletnieks
2019-01-26 18:09 ` Jonathan Cameron
2019-01-28 7:23 ` Alexandru Ardelean
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=1548358316-8062-1-git-send-email-rodrigorsdc@gmail.com \
--to=rodrigorsdc@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--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 \
--cc=rafael.tsuha@usp.br \
/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).