[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4FD5FEDF.6020405@grandegger.com>
Date: Mon, 11 Jun 2012 16:21:19 +0200
From: Wolfgang Grandegger <wg@...ndegger.com>
To: Federico Vaga <federico.vaga@...il.com>
CC: Bhupesh SHARMA <bhupesh.sharma@...com>,
"rubini@...dd.com" <rubini@...dd.com>,
"anilkumar@...com" <anilkumar@...com>,
"mkl@...gutronix.de" <mkl@...gutronix.de>,
"alan@...rguk.ukuu.org.uk" <alan@...rguk.ukuu.org.uk>,
Giancarlo ASNAGHI <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
On 06/11/2012 03:18 PM, Federico Vaga wrote:
> How we proceed?
> I submit my c_can_pci.c as a separated module, we create a
> c_can_platform_common.c,
> or we are thinking about a generic c_can.c as plaftorm driver?
I would accept your patch with the remaining fixes especially the new
register access methods introduced by the D_CAN support patch recently.
Any further improvements to the device abstraction and a more consistent
handling of the platform data or register access should be addressed by
sub-sequent patches.
Wolfgang.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists