From: Wolfgang Grandegger <wg@grandegger.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: netdev@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
linux-can@vger.kernel.org, linuxppc-dev@ozlabs.org,
socketcan-users@lists.berlios.de
Subject: Re: [PATCH net-next v6 4/4] powerpc: tqm8548/tqm8xx: add and update CAN device nodes
Date: Wed, 07 Dec 2011 09:25:03 +0100 [thread overview]
Message-ID: <4EDF22DF.5020001@grandegger.com> (raw)
In-Reply-To: <1323243268.660.71.camel@pasglop>
On 12/07/2011 08:34 AM, Benjamin Herrenschmidt wrote:
> On Thu, 2011-12-01 at 10:41 +0100, Wolfgang Grandegger wrote:
>> This patch enables or updates support for the CC770 and AN82527
>> CAN controller on the TQM8548 and TQM8xx boards.
>
> I'm a bit confused by the net-next prefix here. Those patches seem to
> be only touching arch/powerpc and seem to be sent primarily toward
> netdev with a net-next prefix.
These patches are part of a series implementing a new netdev CAN driver
with device-tree support for CC770/i82527 CAN controllers. The
device-tree support and bindings are properly documented and some DTS
files have been updated accordingly. The relevant maintainers and
mailing list have been addressed.
> Also there have been at least 3 versions in a couple of days already
> without comments nor indication of what was changed...
Unfortunately, no response from those sub-system guys.
> Can you clarify things a bit please ? It looks like they really should
> go to linuxppc-dev (and you can probably drop a bunch of other lists) or
> am I missing an important piece of the puzzle ? (Such as patch 1/4 and
> 2/4 ...)
I have not sent the whole series. The changes are documented in the
cover-letter, which I have not sent for those patches. Well, I think
it's better to sent the whole series to all parties instead?
> Let me know if I should just remove them from powerpc patchwork.
Dave has already applied all patches.
Sorry for the confusion. Any advice on how to handle multi subsystem
series of patches properly is welcome.
Wolfgang.
next prev parent reply other threads:[~2011-12-07 8:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1322732481-2255-1-git-send-email-wg@grandegger.com>
[not found] ` <1322732481-2255-1-git-send-email-wg-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
2011-12-01 9:41 ` [PATCH net-next v6 3/4] can: cc770: add platform bus driver for the CC770 and AN82527 Wolfgang Grandegger
2011-12-01 9:41 ` [PATCH net-next v6 4/4] powerpc: tqm8548/tqm8xx: add and update CAN device nodes Wolfgang Grandegger
2011-12-07 7:34 ` Benjamin Herrenschmidt
2011-12-07 7:39 ` David Miller
2011-12-07 7:42 ` Benjamin Herrenschmidt
2011-12-07 8:25 ` Wolfgang Grandegger [this message]
2011-12-07 22:01 ` Benjamin Herrenschmidt
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=4EDF22DF.5020001@grandegger.com \
--to=wg@grandegger.com \
--cc=benh@kernel.crashing.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-can@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=socketcan-users@lists.berlios.de \
/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).