From: Anatolij Gustschin <agust@denx.de>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, pantelis.antoniou@gmail.com,
vbordug@ru.mvista.com, Gerhard Sittig <gsi@denx.de>
Subject: [PATCH net-next 1/2] fs_enet: silence a build warning (unused variable)
Date: Thu, 22 Aug 2013 21:55:12 +0200 [thread overview]
Message-ID: <1377201313-10420-1-git-send-email-agust@denx.de> (raw)
From: Gerhard Sittig <gsi@denx.de>
Since commit 720a43efd30f04a0a492c85fb997361c44fbae05
(drivers:net: Remove unnecessary OOM messages after netdev_alloc_skb)
there is a build warning:
drivers/net/ethernet/freescale/fs_enet/fs_enet-main.c: In function 'tx_skb_align_workaround':
drivers/net/ethernet/freescale/fs_enet/fs_enet-main.c:586:26: warning: unused variable 'fep'
Fix it.
Signed-off-by: Gerhard Sittig <gsi@denx.de>
Signed-off-by: Anatolij Gustschin <agust@denx.de>
---
.../net/ethernet/freescale/fs_enet/fs_enet-main.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/net/ethernet/freescale/fs_enet/fs_enet-main.c b/drivers/net/ethernet/freescale/fs_enet/fs_enet-main.c
index 8de53a1..c04eb3a 100644
--- a/drivers/net/ethernet/freescale/fs_enet/fs_enet-main.c
+++ b/drivers/net/ethernet/freescale/fs_enet/fs_enet-main.c
@@ -583,7 +583,6 @@ static struct sk_buff *tx_skb_align_workaround(struct net_device *dev,
struct sk_buff *skb)
{
struct sk_buff *new_skb;
- struct fs_enet_private *fep = netdev_priv(dev);
/* Alloc new skb */
new_skb = netdev_alloc_skb(dev, skb->len + 4);
--
1.7.9.5
next reply other threads:[~2013-08-22 19:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-22 19:55 Anatolij Gustschin [this message]
2013-08-22 19:55 ` [PATCH net-next 2/2] fs_enet: cleanup clock API use Anatolij Gustschin
2013-08-23 5:14 ` David Miller
2013-08-23 5:14 ` [PATCH net-next 1/2] fs_enet: silence a build warning (unused variable) David Miller
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=1377201313-10420-1-git-send-email-agust@denx.de \
--to=agust@denx.de \
--cc=davem@davemloft.net \
--cc=gsi@denx.de \
--cc=netdev@vger.kernel.org \
--cc=pantelis.antoniou@gmail.com \
--cc=vbordug@ru.mvista.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).