[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <331ABD5ECB02734CA317220B2BBEABC13E9CB18A@DBDE01.ent.ti.com>
Date: Tue, 5 Jun 2012 15:12:36 +0000
From: "AnilKumar, Chimata" <anilkumar@...com>
To: Alessandro Rubini <rubini@...dd.com>,
"mkl@...gutronix.de" <mkl@...gutronix.de>
CC: "bhupesh.sharma@...com" <bhupesh.sharma@...com>,
"federico.vaga@...il.com" <federico.vaga@...il.com>,
"alan@...rguk.ukuu.org.uk" <alan@...rguk.ukuu.org.uk>,
"wg@...ndegger.com" <wg@...ndegger.com>,
"giancarlo.asnaghi@...com" <giancarlo.asnaghi@...com>,
"alan@...ux.intel.com" <alan@...ux.intel.com>,
"linux-can@...r.kernel.org" <linux-can@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH RFC] c_can_pci: generic module for c_can on PCI
Hi Alessandro/Federico,
On Tue, Jun 05, 2012 at 19:00:13, Alessandro Rubini wrote:
> > I personally like the "pci device sets up a platform device" idea.
>
> Good. Than me or federico will submit a proposal.
>
I am late to the discussion, is there any specific reason to maintain a
separate platform file (c_can_pci.c). I think 90% of the code is copied
from c_can_paltform.c, code changes will be less if you merge to existing
c_can platform driver. You can look at D_CAN integration to C_CAN driver.
[1] https://gitorious.org/linux-can/linux-can-next
Regards
AnilKumar--
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