From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Wolfgang Grandegger <wg@grandegger.com>
Cc: linuxppc-dev@ozlabs.org, netdev@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org,
socketcan-users@lists.berlios.de, linux-can@vger.kernel.org
Subject: Re: [PATCH net-next v6 4/4] powerpc: tqm8548/tqm8xx: add and update CAN device nodes
Date: Thu, 08 Dec 2011 09:01:11 +1100 [thread overview]
Message-ID: <1323295271.12793.1.camel@pasglop> (raw)
In-Reply-To: <4EDF22DF.5020001@grandegger.com>
On Wed, 2011-12-07 at 09:25 +0100, Wolfgang Grandegger wrote:
> > 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?
Well at least for linuxppc-dev, don't bother now that I know what this
is about :-)
> > 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.
No specific advice. Ideally, if patchwork could track cover letters it
would help but I don't see a non-nasty way to do it so ... :-)
Cheers,
Ben.
prev parent reply other threads:[~2011-12-07 22:01 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>
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
2011-12-07 22:01 ` Benjamin Herrenschmidt [this message]
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=1323295271.12793.1.camel@pasglop \
--to=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 \
--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).