From: David Miller <davem@davemloft.net>
To: sergei.shtylyov@cogentembedded.com
Cc: netdev@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
linux-sh@vger.kernel.org
Subject: Re: [PATCH 0/2] sh_eth: unify the SoC feature checks
Date: Mon, 26 Mar 2018 16:34:47 +0000 [thread overview]
Message-ID: <20180326.123447.1350791578528691423.davem@davemloft.net> (raw)
In-Reply-To: <b3706a51-27a4-d78b-998d-9440637ac216@cogentembedded.com>
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Date: Sat, 24 Mar 2018 23:04:53 +0300
> Here's a set of 5 patches against DaveM's 'net-next.git' repo.
>
> The Ether driver sometimes uses the bit fields in 'struct sh_eth_cpu_data'
> to check which Ether registers exist in a certain SoC and sometimes it uses
> sh_eth_is_{gether|rz_fast_ether}() which basically compares 2 pointers (1 of
> them being constant) -- the latter is definitely not a strongest feature of
> the RISC CPUs (be it SH or ARM), so I decided to get rid of this type of
> the feature checks in favour of the bit fields (I've also made use of a
> 32-bit value and method pointer where appropriate)...
Series applied with patch #4 subject fixed up.
Thank you.
prev parent reply other threads:[~2018-03-26 16:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-24 20:04 [PATCH 0/2] sh_eth: unify the SoC feature checks Sergei Shtylyov
2018-03-24 20:07 ` [PATCH 1/5] sh_eth: add sh_eth_cpu_data::soft_reset() method Sergei Shtylyov
2018-03-24 20:08 ` [PATCH 2/5] sh_eth: add sh_eth_cpu_data::edtrr_trns value Sergei Shtylyov
2018-03-24 20:09 ` [PATCH 3/5] sh_eth: add sh_eth_cpu_data::xdfar_rw flag Sergei Shtylyov
2018-03-24 20:11 ` [PATCH 4/5] sh_eth: add sh_eth_cpu_data::no_tx_cntr flag Sergei Shtylyov
2018-03-24 20:15 ` Sergei Shtylyov
2018-03-24 20:12 ` [PATCH 5/5] sh_eth: add sh_eth_cpu_data::cexcr flag Sergei Shtylyov
2018-03-24 20:14 ` [PATCH 0/2] sh_eth: unify the SoC feature checks Sergei Shtylyov
2018-03-24 20:30 ` Sergei Shtylyov
2018-03-26 16:34 ` 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=20180326.123447.1350791578528691423.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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).