From: Carmeli Tamir <carmeli.tamir@gmail.com>
To: gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Cc: areklis909@gmail.com, natechancellor@gmail.com,
dan.carpenter@oracle.com, chrisadr@gentoo.org,
Carmeli Tamir <carmeli.tamir@gmail.com>
Subject: [PATCH 1/3] staging: emxx_udc: Added static modifier to udc_controller
Date: Thu, 1 Nov 2018 15:58:57 -0400 [thread overview]
Message-ID: <1541102337-51475-1-git-send-email-carmeli.tamir@gmail.com> (raw)
Added static modifier to the udc_controller, since it's only
required within emxx_udc.c.
Previously posted without any feedback, now updated according to master.
Signed-off-by: Carmeli Tamir <carmeli.tamir@gmail.com>
---
drivers/staging/emxx_udc/emxx_udc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/emxx_udc/emxx_udc.c b/drivers/staging/emxx_udc/emxx_udc.c
index 3e51476..94a4327 100644
--- a/drivers/staging/emxx_udc/emxx_udc.c
+++ b/drivers/staging/emxx_udc/emxx_udc.c
@@ -56,7 +56,7 @@ static void _nbu2ss_fifo_flush(struct nbu2ss_udc *, struct nbu2ss_ep *);
/*===========================================================================*/
/* Global */
-struct nbu2ss_udc udc_controller;
+static struct nbu2ss_udc udc_controller;
/*-------------------------------------------------------------------------*/
/* Read */
--
2.7.4
next reply other threads:[~2018-11-01 19:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 19:58 Carmeli Tamir [this message]
2018-11-07 11:29 ` [PATCH 1/3] staging: emxx_udc: Added static modifier to udc_controller Greg KH
-- strict thread matches above, loose matches on Subject: below --
2018-11-07 20:44 [PATCH 0/3] staging: emxx_udc: Fixed all meaningful sparse warnings Carmeli Tamir
2018-11-07 20:44 ` [PATCH 1/3] staging: emxx_udc: Added static modifier to udc_controller Carmeli Tamir
2018-11-12 9:42 ` Geert Uytterhoeven
2018-10-17 21:01 Carmeli Tamir
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=1541102337-51475-1-git-send-email-carmeli.tamir@gmail.com \
--to=carmeli.tamir@gmail.com \
--cc=areklis909@gmail.com \
--cc=chrisadr@gentoo.org \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=natechancellor@gmail.com \
/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).