From: Lukasz Majewski <lukma@denx.de>
To: u-boot@lists.denx.de
Subject: [PATCH 1/1] x86: remove dead code in intel_clk_get_rate()
Date: Sun, 16 Feb 2020 09:49:26 +0100 [thread overview]
Message-ID: <20200216094926.3669786d@jawa> (raw)
In-Reply-To: <20200215202200.15150-1-xypron.glpk@gmx.de>
On Sat, 15 Feb 2020 21:22:00 +0100
Heinrich Schuchardt <xypron.glpk@gmx.de> wrote:
> If all branches of a switch statement have a return instruction, all
> subsequent lines are unreachable.
>
> Identified with cppcheck.
>
> Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
> ---
> drivers/clk/intel/clk_intel.c | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/drivers/clk/intel/clk_intel.c
> b/drivers/clk/intel/clk_intel.c index d2e15491a3..b633934d90 100644
> --- a/drivers/clk/intel/clk_intel.c
> +++ b/drivers/clk/intel/clk_intel.c
> @@ -11,8 +11,6 @@
>
> static ulong intel_clk_get_rate(struct clk *clk)
> {
> - ulong rate;
> -
> switch (clk->id) {
> case CLK_I2C:
> /* Hard-coded to 133MHz on current platforms */
> @@ -20,8 +18,6 @@ static ulong intel_clk_get_rate(struct clk *clk)
> default:
> return -ENODEV;
> }
> -
> - return rate;
> }
>
> static struct clk_ops intel_clk_ops = {
> --
> 2.25.0
>
Reviewed-by: Lukasz Majewski <lukma@denx.de>
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma at denx.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200216/04d7158d/attachment.sig>
next prev parent reply other threads:[~2020-02-16 8:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-15 20:22 [PATCH 1/1] x86: remove dead code in intel_clk_get_rate() Heinrich Schuchardt
2020-02-16 8:49 ` Lukasz Majewski [this message]
2020-02-16 19:03 ` Simon Glass
2020-02-20 13:40 ` Bin Meng
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=20200216094926.3669786d@jawa \
--to=lukma@denx.de \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.