All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: "AnilKumar, Chimata" <anilkumar@ti.com>
Cc: "m.kleine-budde@pengutronix.de" <m.kleine-budde@pengutronix.de>,
	"wg@grandegger.com" <wg@grandegger.com>,
	"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Gole, Anant" <anantgole@ti.com>, "Nori, Sekhar" <nsekhar@ti.com>
Subject: Re: [PATCH] ARM: OMAP: AM33XX: CAN: d_can: Add support for Bosch D_CAN controller
Date: Tue, 03 Apr 2012 17:54:23 +0200	[thread overview]
Message-ID: <4F7B1D2F.40409@hartkopp.net> (raw)
In-Reply-To: <331ABD5ECB02734CA317220B2BBEABC1317D84CC@DBDE01.ent.ti.com>

On 03.04.2012 14:39, AnilKumar, Chimata wrote:

> Hi All,
> 
> Subject line of this patch should be
> "ARM: CAN: d_can: Add support for Bosch D_CAN controller"


No, the d_can IP core is generally not limited to ARM.

	"can: Add support for Bosch D_CAN controller"

would be perfectly fine.

The correct way is:

1. post your new CAN driver to linux-can ML
2. When the major reviews & style fixes are done and the driver is fit for
mainline you can post it on ti-omap ML too

But an initial cross-posting of this CAN driver to netdev ML and linux-kernel
ML does not help anyone - it only increases traffic & confusion.

See MAINTAINERS:

http://lxr.linux.no/#linux+v3.3.1/MAINTAINERS#L1710

Thanks for following these hints,
Oliver

  reply	other threads:[~2012-04-03 15:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-03 12:32 [PATCH] ARM: OMAP: AM33XX: CAN: d_can: Add support for Bosch D_CAN controller AnilKumar Ch
2012-04-03 12:32 ` AnilKumar Ch
2012-04-03 12:39 ` AnilKumar, Chimata
2012-04-03 15:54   ` Oliver Hartkopp [this message]
2012-04-03 18:07     ` AnilKumar, Chimata
2012-04-03 12:44 ` Wolfgang Grandegger
2012-04-03 12:49   ` Marc Kleine-Budde
2012-04-03 13:41   ` AnilKumar, Chimata
2012-04-03 13:49     ` Marc Kleine-Budde
2012-04-03 14:29       ` AnilKumar, Chimata
2012-04-03 15:33         ` Marc Kleine-Budde
2012-04-03 15:58           ` AnilKumar, Chimata
2012-04-04  3:43             ` Bhupesh SHARMA
2012-04-04 16:21             ` Wolfgang Grandegger
2012-04-05 14:15               ` AnilKumar, Chimata
2012-04-05 14:20                 ` Gary Thomas
2012-04-05 15:54                   ` Gole, Anant
2012-04-05 16:00                     ` Gary Thomas

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=4F7B1D2F.40409@hartkopp.net \
    --to=socketcan@hartkopp.net \
    --cc=anantgole@ti.com \
    --cc=anilkumar@ti.com \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=m.kleine-budde@pengutronix.de \
    --cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.