From: David Lechner <dlechner@baylibre.com>
To: linux-iio@vger.kernel.org
Cc: David Lechner <dlechner@baylibre.com>,
Jonathan Cameron <jic23@kernel.org>,
Michael Hennerich <Michael.Hennerich@analog.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH 1/2] iio: resolver: ad2s1210: remove DRV_NAME macro
Date: Thu, 12 Oct 2023 11:18:12 -0500 [thread overview]
Message-ID: <20231012-ad2s1210-mainline-v1-1-b2ee31c0e9dd@baylibre.com> (raw)
In-Reply-To: <20231012-ad2s1210-mainline-v1-0-b2ee31c0e9dd@baylibre.com>
The DRV_NAME macro is only used in one place in the ad2s1210 driver and
is not really needed so let's remove it.
Suggested-by: Jonathan Cameron <jic23@kernel.org>
Signed-off-by: David Lechner <dlechner@baylibre.com>
---
drivers/iio/resolver/ad2s1210.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/iio/resolver/ad2s1210.c b/drivers/iio/resolver/ad2s1210.c
index bd4a90c222b5..00562bc542bb 100644
--- a/drivers/iio/resolver/ad2s1210.c
+++ b/drivers/iio/resolver/ad2s1210.c
@@ -68,8 +68,6 @@
#include <linux/iio/trigger_consumer.h>
#include <linux/iio/triggered_buffer.h>
-#define DRV_NAME "ad2s1210"
-
/* control register flags */
#define AD2S1210_ADDRESS_DATA BIT(7)
#define AD2S1210_PHASE_LOCK_RANGE_44 BIT(5)
@@ -1509,7 +1507,7 @@ MODULE_DEVICE_TABLE(spi, ad2s1210_id);
static struct spi_driver ad2s1210_driver = {
.driver = {
- .name = DRV_NAME,
+ .name = "ad2s1210",
.of_match_table = of_match_ptr(ad2s1210_of_match),
},
.probe = ad2s1210_probe,
--
2.42.0
next prev parent reply other threads:[~2023-10-12 16:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 16:18 [PATCH 0/2] iio: resolver: ad2s1210: small cleanups David Lechner
2023-10-12 16:18 ` David Lechner [this message]
2023-10-12 16:18 ` [PATCH 2/2] iio: resolver: ad2s1210: remove of_match_ptr() David Lechner
2023-10-14 12:54 ` [PATCH 0/2] iio: resolver: ad2s1210: small cleanups 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=20231012-ad2s1210-mainline-v1-1-b2ee31c0e9dd@baylibre.com \
--to=dlechner@baylibre.com \
--cc=Michael.Hennerich@analog.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--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®