From: Albert ARIBAUD <albert.aribaud@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/4] ARM: Rename kirkwood_egiga driver to egiga
Date: Mon, 05 Jul 2010 13:36:23 +0200 [thread overview]
Message-ID: <4C31C3B7.1040007@free.fr> (raw)
In-Reply-To: <F766E4F80769BD478052FB6533FA745D19A4A5CC57@SC-VEXCH4.marvell.com>
Le 05/07/2010 13:02, Prafulla Wadaskar a ?crit :
> if it is generic gigabit Ethernet driver abstraction, could be applicable to any kind of SOC then the same egiga is relevant. which is not the case here
> if it is Marvell specific then the name should be like- mv_egiga
As it is Marvell-IP specific, I'll rename it to mv_egiga.
> I think we should sync on the arch first, that would same lot of coding/review efforts
> I have below mentioned architecture for this driver -
> 1. Abstract generic SoC independent driver skeleton into mv"_egiga.c/h
> 2. Abstract and put Kirkwood specific functions is arch/arm/cpu/kirkwood/egiga.c
> 3. Create and put Orion specific functions is arch/arm/cpu/orion5x/egiga.c
> 4. Use common APIs/Macros to call SoC specific functions in generic driver
> 5. same strategy should be applied for header files abstraction.
Agree.
> there should be generic CONFIG to address this build, and CONFIG_KIRKWOOD_EGIGA
> should address its SOC specific dependency, you have done this in patch 3/4
Yes, I have. Do you mean you would prefer everything--file renaming,
symbol renaming--in a single commit?
> As suggested by Ben rest should be rename activity than delete/add for 1/x patch
Ok.
Thanks for the feedback. I'll provide an updated patchset once I get
your answer to my question above.
Amicalement,
--
Albert.
next prev parent reply other threads:[~2010-07-05 11:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-02 16:53 [U-Boot] [PATCH 0/4] make egiga common to kirkwood and orion5x Albert Aribaud
2010-07-02 16:53 ` [U-Boot] [PATCH 1/4] ARM: Rename kirkwood_egiga driver to egiga Albert Aribaud
2010-07-02 16:53 ` [U-Boot] [PATCH 2/4] egiga: Remove functional dependency on kirkwood Albert Aribaud
2010-07-02 16:53 ` [U-Boot] [PATCH 3/4] egiga: remove references to kirkwood SoC Albert Aribaud
2010-07-02 16:53 ` [U-Boot] [PATCH 4/4] egiga: add support for orion5x Albert Aribaud
2010-07-05 11:01 ` Prafulla Wadaskar
2010-07-05 11:02 ` [U-Boot] [PATCH 3/4] egiga: remove references to kirkwood SoC Prafulla Wadaskar
2010-07-05 11:41 ` Albert ARIBAUD
2010-07-05 12:02 ` Prafulla Wadaskar
2010-07-05 11:03 ` [U-Boot] [PATCH 2/4] egiga: Remove functional dependency on kirkwood Prafulla Wadaskar
2010-07-05 17:59 ` Albert ARIBAUD
2010-07-05 19:54 ` Prafulla Wadaskar
2010-07-02 17:20 ` [U-Boot] [PATCH 1/4] ARM: Rename kirkwood_egiga driver to egiga Ben Warren
2010-07-02 17:27 ` Albert ARIBAUD
2010-07-05 11:02 ` Prafulla Wadaskar
2010-07-05 11:36 ` Albert ARIBAUD [this message]
2010-07-05 12:01 ` Prafulla Wadaskar
2010-07-05 13:15 ` Albert ARIBAUD
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=4C31C3B7.1040007@free.fr \
--to=albert.aribaud@free.fr \
--cc=u-boot@lists.denx.de \
/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