linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 01/11] ARM: shmobile: r8a7778: cleanup registration of sh_eth
Date: Thu, 18 Jul 2013 12:26:17 +0000	[thread overview]
Message-ID: <51E7DEE9.8060208@cogentembedded.com> (raw)
In-Reply-To: <87li5dfqft.wl%kuninori.morimoto.gx@renesas.com>

Hello.

On 18-07-2013 10:35, Kuninori Morimoto wrote:

>> But is it really that much easier?
>> Does this series remove all the other unused code from setup.c?
>> Does it really matter if we forget to remove some bits of setup.c
>> once they are unused?

> The point is not "unused code", but "non-shared sharing code".
> I guess people use copy-paste base development.
> So, if we don't clean-up these "non-shared sharing code" now,
> we will have more and more r8a77xx_add_xxx_device(pdata) type method
> (which is the "non-shared sharing code" :)

    And that will teach them doing things the right, scalable way from the start.

> in both board-xxx.c and setup-xxx.c before we have DT support.
> This means clean-up these "after" DT support will be more complex.
> I don't want this type of nightmare.

    And I don't want "SoC device in the board code" non-scalable nightmare
when people will start producing their own boards based on Renesas SoCs. I 
don't want to give them the bad example that your USB code was before my 
9-patch cleanup, and another several bad examples which you're now to trying 
to push into renesas.git. I don't want my efforts wasted.

> Do you mean r8a7779 sh_eth clean-up code ?
> If so, 1) I can't find "board" code which is using r8a7779_add_ether_device(xx),
> 2) I guess marzen board doesn't have sh_eth HW implementation.

    It has several types of daughter boards with Ethernet PHY and connector. 
See my off-list email.

> Best regards
> ---
> Kuninori Morimoto

WBR, Sergei


  parent reply	other threads:[~2013-07-18 12:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-11  8:31 [PATCH 01/11] ARM: shmobile: r8a7778: cleanup registration of sh_eth Kuninori Morimoto
2013-07-11 11:25 ` Sergei Shtylyov
2013-07-12  0:56 ` Simon Horman
2013-07-12 11:05 ` Sergei Shtylyov
2013-07-17 23:11 ` Simon Horman
2013-07-18  1:52 ` Kuninori Morimoto
2013-07-18  2:30 ` Simon Horman
2013-07-18  6:35 ` Kuninori Morimoto
2013-07-18 11:54 ` Sergei Shtylyov
2013-07-18 12:26 ` Sergei Shtylyov [this message]
2013-07-19  2:30 ` Simon Horman
2013-07-24  4:45 ` Magnus Damm
2013-07-24 12:58 ` Sergei Shtylyov
2013-07-24 14:13 ` Magnus Damm

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=51E7DEE9.8060208@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=linux-sh@vger.kernel.org \
    /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).