linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: netdev@vger.kernel.org
Cc: nobuhiro.iwamatsu.yj@renesas.com, linux-sh@vger.kernel.org
Subject: Re: [PATCH v4 7/8] sh_eth: consolidate sh_eth_reset()
Date: Wed, 05 Jun 2013 22:50:42 +0000	[thread overview]
Message-ID: <51AFC0C2.1050103@cogentembedded.com> (raw)
In-Reply-To: <201306060119.30971.sergei.shtylyov@cogentembedded.com>

Hello.

On 06/06/2013 01:19 AM, Sergei Shtylyov wrote:

> From: Nobuhiro Iwamatsu <nobuhiro.iwamatsu.yj@renesas.com>
>
> This driver has sh_eth_reset() function for each SoC and this function is almost
> always the same, except for the several a bit different variations for Gigabit
> Ethernet.  Consolidate every variation into a single function -- which allows
> us to get rid of some more #ifdef'fery.
>
> Signed-off-by: Nobuhiro Iwamatsu <nobuhiro.iwamatsu.yj@renesas.com>
> [Sergei: moved the new sh_eth_reset() upper to decrease the patch  size,  fixed
> function call continuation lines' indentation, reworded the changelog, reworded
> the subject, changing the prefix.]
> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>
> ---
> Changes in version 4:
> - moved the new sh_eth_reset() upper to desrease the patch size;

Oops, I forgot to test-compile this change:

drivers/net/ethernet/renesas/sh_eth.c: In function ‘sh_eth_reset’:
drivers/net/ethernet/renesas/sh_eth.c:745:2: error: implicit declaration 
of function ‘sh_eth_is_gether’ [-Werror=implicit-function-declaration]
drivers/net/ethernet/renesas/sh_eth.c: At top level:
drivers/net/ethernet/renesas/sh_eth.c:857:12: error: static declaration 
of ‘sh_eth_is_gether’ follows non-static declaration
drivers/net/ethernet/renesas/sh_eth.c:745:6: note: previous implicit 
declaration of ‘sh_eth_is_gether’ was here
cc1: some warnings being treated as errors
make[1]: *** [drivers/net/ethernet/renesas/sh_eth.o] Error 1
make: *** [drivers/net/ethernet/renesas/sh_eth.o] Error 2

I guess I have to repost the whole series now? :-(

WBR, Sergei


  reply	other threads:[~2013-06-05 22:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-05 21:06 [PATCH v4 0/8] sh_eth: deal with #ifdef'fery Sergei Shtylyov
2013-06-05 21:09 ` [PATCH v4 1/8] sh_eth: remove #ifdef around EDSR and GECMR bit definitions Sergei Shtylyov
2013-06-05 21:11 ` [PATCH v4 2/8] sh_eth: use EDSR_ENALL to set EDSR Sergei Shtylyov
2013-06-05 21:12 ` [PATCH v4 3/8] sh_eth: remove duplicate sh_eth_set_duplex() definitions Sergei Shtylyov
2013-06-05 21:14 ` [PATCH v4 4/8] sh_eth: remove SH_ETH_HAS_TSU Sergei Shtylyov
2013-06-05 21:15 ` [PATCH v4 5/8] sh_eth: add IRQ flags to 'struct sh_eth_cpu_data' Sergei Shtylyov
2013-06-05 21:16 ` [PATCH v4 6/8] sh_eth: remove #ifdef around sh_eth_select_mii() Sergei Shtylyov
2013-06-05 21:19 ` [PATCH v4 7/8] sh_eth: consolidate sh_eth_reset() Sergei Shtylyov
2013-06-05 22:50   ` Sergei Shtylyov [this message]
2013-06-05 21:20 ` [PATCH v4 8/8] sh_eth: enclose PM code into #ifdef CONFIG_PM Sergei Shtylyov
2013-06-05 22:50 ` [PATCH v4 0/8] sh_eth: deal with #ifdef'fery Sergei Shtylyov
2013-06-06  3:25 ` Magnus Damm
2013-06-06 14:36   ` Sergei Shtylyov
2013-06-15  0:00   ` Sergei Shtylyov
2013-06-15  0:02     ` Sergei Shtylyov

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=51AFC0C2.1050103@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=linux-sh@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nobuhiro.iwamatsu.yj@renesas.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).