devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: "AnilKumar, Chimata" <anilkumar@ti.com>
Cc: "wg@grandegger.com" <wg@grandegger.com>,
	"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
	"devicetree-discuss@lists.ozlabs.org"
	<devicetree-discuss@lists.ozlabs.org>,
	"grant.likely@secretlab.ca" <grant.likely@secretlab.ca>,
	"Gole, Anant" <anantgole@ti.com>, "Nori, Sekhar" <nsekhar@ti.com>
Subject: Re: [PATCH v3 0/3] Add DT support to C_CAN/D_CAN controller
Date: Thu, 02 Aug 2012 13:23:38 +0200	[thread overview]
Message-ID: <501A633A.5000100@pengutronix.de> (raw)
In-Reply-To: <331ABD5ECB02734CA317220B2BBEABC13EA081AD@DBDE01.ent.ti.com>

[-- Attachment #1: Type: text/plain, Size: 2166 bytes --]

On 08/02/2012 01:21 PM, AnilKumar, Chimata wrote:
> Marc,
> 
> On Thu, Aug 02, 2012 at 16:43:04, Marc Kleine-Budde wrote:
>> On 08/02/2012 01:02 PM, AnilKumar Ch wrote:
>>> This patch series adds the device tree support and Runtime PM support
>>> to C_CAN/D_CAN controller.
>>>
>>> These patches have been tested on AM335x EVM using some additional
>>> patches to add device tree data to EVM dts files and to initialize
>>> D_CAN RAM. D_CAN raminit is controlled from control module register.
>>> This patch will be submitted once control module MFD driver support
>>> is added.
>>>
>>> These patches are based on linx-can-next tree.
>>>
>>> Due to lack of hardware I am not able to test c_can functionality.
>>> I appreciate if anyone can test c_can functionality with this patch
>>> series.
>>>
>>> Changes from v2:
>>> 	- Incorporated Marcs on v2
>>> 	  * Fix compilation errors in pci due to device name changes
>>> 	  in v2 by adding new patch.
>>>
>>> Changes from v1:
>>> 	- Separated 4 patches into CAN driver specific and device
>>> 	  tree data addition specific.
>>> 	- Incorporated Marc's comments on v1
>>> 	  * Modified c_can_dev_id enum to handle both devtype and
>>> 	    platform device id index.
>>> 	  * Removed "legacy bosch,c_can_platform" from DT bindings
>>>
>>> AnilKumar Ch (3):
>>>   can: c_can: Add device tree support to Bosch C_CAN/D_CAN controller
>>>   can: c_can: Modify c_can device names in c_can_pci driver
>>
>> You break bisectability here. After patch 1 the pci driver will not
>> compile anymore. I suggest to do the renaming of enum c_can_dev_id and
>> all it's users in patch 1.
>>
> 
> I will merge patch 1 and 2 and submit v4.

But changing the pci driver has nothing to do with the subject ("Add
device tree support to Bosch C_CAN/D_CAN controller").

It's considered bad practise to do so.

Marc
-- 
Pengutronix e.K.                  | Marc Kleine-Budde           |
Industrial Linux Solutions        | Phone: +49-231-2826-924     |
Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  reply	other threads:[~2012-08-02 11:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-02 11:02 [PATCH v3 0/3] Add DT support to C_CAN/D_CAN controller AnilKumar Ch
2012-08-02 11:02 ` [PATCH v3 1/3] can: c_can: Add device tree support to Bosch " AnilKumar Ch
2012-08-02 11:33   ` Arnd Bergmann
2012-08-02 12:01     ` AnilKumar, Chimata
     [not found] ` <1343905339-4642-1-git-send-email-anilkumar-l0cyMroinI0@public.gmane.org>
2012-08-02 11:02   ` [PATCH v3 2/3] can: c_can: Modify c_can device names in c_can_pci driver AnilKumar Ch
2012-08-02 11:02 ` [PATCH v3 3/3] can: c_can: Add runtime PM support to Bosch C_CAN/D_CAN controller AnilKumar Ch
2012-08-02 11:13 ` [PATCH v3 0/3] Add DT support to " Marc Kleine-Budde
     [not found]   ` <501A60C0.1040504-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-08-02 11:21     ` AnilKumar, Chimata
2012-08-02 11:23       ` Marc Kleine-Budde [this message]
     [not found]         ` <501A633A.5000100-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-08-02 11:39           ` AnilKumar, Chimata
     [not found]             ` <331ABD5ECB02734CA317220B2BBEABC13EA081FB-Er742YJ7I/eIQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2012-08-02 11:45               ` Marc Kleine-Budde
  -- strict thread matches above, loose matches on Subject: below --
2012-08-02 13:13 AnilKumar Ch

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=501A633A.5000100@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=anantgole@ti.com \
    --cc=anilkumar@ti.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-can@vger.kernel.org \
    --cc=nsekhar@ti.com \
    --cc=wg@grandegger.com \
    /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).