Re: [PATCH 3/3] sh_eth: stop using bare numbers for EESIPR values

2017-01-24 Thread Sergei Shtylyov
On 01/23/2017 11:00 AM, Geert Uytterhoeven wrote: Now that we have almost all EESIPR bits declared (and those that are still not are most probably reserved anyway) we can at last replace the bare numbers used for 'sh_eth_cpu_data::eesipr_value' initializers with the bit names ORed together..

Re: [PATCH 3/3] sh_eth: stop using bare numbers for EESIPR values

2017-01-23 Thread Geert Uytterhoeven
Hi Sergei, On Sun, Jan 22, 2017 at 8:19 PM, Sergei Shtylyov wrote: > Now that we have almost all EESIPR bits declared (and those that are > still not are most probably reserved anyway) we can at last replace the > bare numbers used for 'sh_eth_cpu_data::eesipr_value' initializers with > the b

[PATCH 3/3] sh_eth: stop using bare numbers for EESIPR values

2017-01-22 Thread Sergei Shtylyov
Now that we have almost all EESIPR bits declared (and those that are still not are most probably reserved anyway) we can at last replace the bare numbers used for 'sh_eth_cpu_data::eesipr_value' initializers with the bit names ORed together... Signed-off-by: Sergei Shtylyov --- drivers/net/