From: kbuild test robot <lkp@intel.com>
To: jon@ringle.org
Cc: kbuild-all@01.org, broonie@kernel.org,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, Jon Ringle <jringle@gridpoint.com>
Subject: [RFC PATCH] net: encx24j600_exit() can be static
Date: Thu, 1 Oct 2015 20:26:20 +0800 [thread overview]
Message-ID: <20151001122620.GA9861@xian> (raw)
In-Reply-To: <1443699801-8888-2-git-send-email-jon@ringle.org>
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
encx24j600.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/microchip/encx24j600.c b/drivers/net/ethernet/microchip/encx24j600.c
index 1da37fd..afc008a 100644
--- a/drivers/net/ethernet/microchip/encx24j600.c
+++ b/drivers/net/ethernet/microchip/encx24j600.c
@@ -1112,7 +1112,7 @@ static int __init encx24j600_init(void)
}
module_init(encx24j600_init);
-void encx24j600_exit(void)
+static void encx24j600_exit(void)
{
spi_unregister_driver(&encx24j600_spi_net_driver);
}
next prev parent reply other threads:[~2015-10-01 12:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 11:43 [PATCH net-next v2 1/2] regmap: Allow installing custom reg_update_bits function jon
2015-10-01 11:43 ` [PATCH net-next v2 2/2] net: Microchip encx24j600 driver jon
2015-10-01 12:26 ` kbuild test robot [this message]
2015-10-05 10:54 ` David Miller
2015-10-05 11:00 ` David Miller
2015-10-05 11:01 ` David Miller
2015-10-05 10:54 ` [PATCH net-next v2 1/2] regmap: Allow installing custom reg_update_bits function David Miller
2015-10-05 11:57 ` Jon Ringle
2015-10-05 13:16 ` David Miller
2015-10-05 14:25 ` Mark Brown
2015-10-06 6:21 ` David Miller
2015-10-06 9:57 ` Mark Brown
2015-10-06 13:22 ` David Miller
2015-10-06 15:07 ` Mark Brown
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=20151001122620.GA9861@xian \
--to=lkp@intel.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jon@ringle.org \
--cc=jringle@gridpoint.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).