From: David Miller <davem@davemloft.net>
To: sergei.shtylyov@cogentembedded.com
Cc: netdev@vger.kernel.org, nobuhiro.iwamatsu.yj@renesas.com,
linux-sh@vger.kernel.org
Subject: Re: [PATCH v5 0/8] sh_eth: deal with #ifdef'fery
Date: Thu, 06 Jun 2013 16:05:04 -0700 (PDT) [thread overview]
Message-ID: <20130606.160504.85747659460186927.davem@davemloft.net> (raw)
In-Reply-To: <201306062339.21353.sergei.shtylyov@cogentembedded.com>
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Date: Thu, 6 Jun 2013 23:39:20 +0400
> This series of 8 patches are against Dave's 'net-next.git' repository.
> The series deals mostly with excess #ifdef'fery in the 'sh_eth' driver.
> It doesn't yet get rid of all the #ifdef'fery but that's a matter of another
> patchset. The last patch (it was almost in the middle of the series before),
> contrariwise, adds one missing #ifdef...
>
> [1/8] sh_eth: remove #ifdef around EDSR and GECMR bit definitions
> [2/8] sh_eth: use EDSR_ENALL to set EDSR
> [3/8] sh_eth: remove duplicate sh_eth_set_duplex() definitions
> [4/8] sh_eth: remove SH_ETH_HAS_TSU
> [5/8] sh_eth: add IRQ flags to 'struct sh_eth_cpu_data'
> [6/8] sh_eth: remove #ifdef around sh_eth_select_mii()
> [7/8] sh_eth: consolidate sh_eth_reset()
> [8/8] sh_eth: enclose PM code into #ifdef CONFIG_PM
All applied, thanks.
I think you should have two sets of const netdev_ops to cover the two
cases, instead of writing to a non-const netdev_ops. Could you send a
follow-on patch which does that?
Thanks.
next prev parent reply other threads:[~2013-06-06 23:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 19:39 [PATCH v5 0/8] sh_eth: deal with #ifdef'fery Sergei Shtylyov
2013-06-06 19:43 ` [PATCH v5 1/8] sh_eth: remove #ifdef around EDSR and GECMR bit definitions Sergei Shtylyov
2013-06-06 19:44 ` [PATCH v5 2/8] sh_eth: use EDSR_ENALL to set EDSR Sergei Shtylyov
2013-06-06 19:45 ` [PATCH v5 3/8] sh_eth: remove duplicate sh_eth_set_duplex() definitions Sergei Shtylyov
2013-06-06 19:48 ` [PATCH v5 4/8] sh_eth: remove SH_ETH_HAS_TSU Sergei Shtylyov
2013-06-06 19:49 ` [PATCH v5 5/8] sh_eth: add IRQ flags to 'struct sh_eth_cpu_data' Sergei Shtylyov
2013-06-06 19:50 ` [PATCH v5 6/8] sh_eth: remove #ifdef around sh_eth_select_mii() Sergei Shtylyov
2013-06-06 19:51 ` [PATCH v5 7/8] sh_eth: consolidate sh_eth_reset() Sergei Shtylyov
2013-06-06 19:52 ` [PATCH v5 8/8] sh_eth: enclose PM code into #ifdef CONFIG_PM Sergei Shtylyov
2013-06-06 23:05 ` David Miller [this message]
2013-06-07 12:24 ` [PATCH v5 0/8] sh_eth: deal with #ifdef'fery 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=20130606.160504.85747659460186927.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-sh@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nobuhiro.iwamatsu.yj@renesas.com \
--cc=sergei.shtylyov@cogentembedded.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).