From: Sean Behan <codebam@riseup.net>
To: unlisted-recipients:; (no To-header on input)
Cc: codebam@riseup.net, nathan@kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Alex Dewar <alex.dewar90@gmail.com>,
Kumar Kartikeya Dwivedi <memxor@gmail.com>,
Colin Ian King <colin.king@canonical.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: [PATCH] staging: emxx_udc: remove unused variable driver_desc
Date: Wed, 17 Feb 2021 09:24:17 -0500 [thread overview]
Message-ID: <20210217142420.7350-1-codebam@riseup.net> (raw)
When building with W=1, there is a warning that this variable is unused.
It is not used so remove it to fix the warning.
Thanks to nathan@kernel.org for helping me submit my first patch.
Signed-off-by: Sean Behan <codebam@riseup.net>
---
drivers/staging/emxx_udc/emxx_udc.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/staging/emxx_udc/emxx_udc.c b/drivers/staging/emxx_udc/emxx_udc.c
index 3536c03ff523..741147a4f0fe 100644
--- a/drivers/staging/emxx_udc/emxx_udc.c
+++ b/drivers/staging/emxx_udc/emxx_udc.c
@@ -38,7 +38,6 @@ static struct gpio_desc *vbus_gpio;
static int vbus_irq;
static const char driver_name[] = "emxx_udc";
-static const char driver_desc[] = DRIVER_DESC;
/*===========================================================================*/
/* Prototype */
--
2.29.2
next reply other threads:[~2021-02-17 14:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 14:24 Sean Behan [this message]
2021-02-17 14:37 ` [PATCH] staging: emxx_udc: remove unused variable driver_desc Greg Kroah-Hartman
-- strict thread matches above, loose matches on Subject: below --
2021-02-19 3:41 Sean Behan
2021-02-19 6:03 ` Greg Kroah-Hartman
2021-02-17 14:21 Sean Behan
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=20210217142420.7350-1-codebam@riseup.net \
--to=codebam@riseup.net \
--cc=alex.dewar90@gmail.com \
--cc=colin.king@canonical.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=memxor@gmail.com \
--cc=nathan@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).