[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201001270306.22089.arnd@arndb.de>
Date: Wed, 27 Jan 2010 03:06:21 +0100
From: Arnd Bergmann <arnd@...db.de>
To: Wolfgang Denk <wd@...x.de>
Cc: Wolfgang Grandegger <wg@...ndegger.com>,
linuxppc-dev@...ts.ozlabs.org, David Miller <davem@...emloft.net>,
dzu@...x.de, netdev@...r.kernel.org, linuxppc-dev@...abs.org,
agust@...x.de, kosmo@...ihalf.com,
Grant Likely <grant.likely@...retlab.ca>
Subject: Re: [net-next-2.6 PATCH 2/3] fs_enet: Add support for MPC512x to fs_enet driver
On Sunday 24 January 2010, Wolfgang Denk wrote:
> In message <4B5C5BDF.6020001@...ndegger.com> you wrote:
> >
> > You are probably right and your proposal would likely result in more
> > transparent (less ugly) code. There has been some discussion about
> > unifying FEC drivers when the patches (with the same subject) have been
> > submitted for the first time in May last year, but it was not about 512x
> > and 8xx, IIRC.
>
> You can re-read this discussion here:
>
> http://patchwork.ozlabs.org/patch/26927/
>
> ee especiall Grant's note of 2009-05-21 15:36:11: "If it looks too
> ugly, then just fork the driver."
Ok. I fully agree with what Grant said in that thread, especially the
way the files could be split. Forking the entire driver would work
as an easy way to get it running at first, and we still have the option
of reorganizing the duplicate parts later in a saner way if that's seen
as helpful. I'd assume that at least some parts of it could become a
lib_fs_enet module that can be shared by all of them.
Arnd
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists