Netdev List
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: vz@mleia.com
Cc: slemieux.tyco@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH] net: ethernet: lpc_eth: remove unused local variable
Date: Fri, 19 Oct 2018 17:05:13 -0700 (PDT)	[thread overview]
Message-ID: <20181019.170513.2231540324890213277.davem@davemloft.net> (raw)
In-Reply-To: <20181018230653.10637-1-vz@mleia.com>

From: Vladimir Zapolskiy <vz@mleia.com>
Date: Fri, 19 Oct 2018 02:06:53 +0300

> A trivial change which removes an unused local variable, the issue
> is reported as a compile time warning:
> 
>   drivers/net/ethernet/nxp/lpc_eth.c: In function 'lpc_eth_drv_probe':
>   drivers/net/ethernet/nxp/lpc_eth.c:1250:21: warning: variable 'phydev' set but not used [-Wunused-but-set-variable]
>     struct phy_device *phydev;
>                        ^~~~~~
> 
> Signed-off-by: Vladimir Zapolskiy <vz@mleia.com>

Applied.

      reply	other threads:[~2018-10-20  8:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-18 23:06 [PATCH] net: ethernet: lpc_eth: remove unused local variable Vladimir Zapolskiy
2018-10-20  0:05 ` David Miller [this message]

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=20181019.170513.2231540324890213277.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=slemieux.tyco@gmail.com \
    --cc=vz@mleia.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