From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Vinh Huu Tuong Nguyen <vhtnguyen@apm.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: RE: [PATCH] powerpc/44x: Support OCM(On Chip Memory) for APM821xx SoC and Bluestone board
Date: Wed, 13 Jun 2012 10:40:38 +1000 [thread overview]
Message-ID: <1339548038.9220.80.camel@pasglop> (raw)
In-Reply-To: <da2d8ae5f5008c4695d1898b9e121c1f@mail.gmail.com>
On Tue, 2012-06-12 at 17:26 +0700, Vinh Huu Tuong Nguyen wrote:
> > -----Original Message-----
> > From: Vinh Nguyen Huu Tuong [mailto:vhtnguyen@apm.com]
> > Sent: Monday, May 07, 2012 10:53 AM
> > To: Benjamin Herrenschmidt; Paul Mackerras; Josh Boyer; Matt Porter;
> > Grant Likely; Rob Herring; Duc Dang; David S. Miller; Kumar Gala; Li
> > Yang; Ashish Kalra; Anatolij Gustschin; Liu Gang; linuxppc-
> > dev@lists.ozlabs.org; linux-kernel@vger.kernel.org; devicetree-
> > discuss@lists.ozlabs.org
> > Cc: Vinh Nguyen Huu Tuong
> > Subject: [PATCH] powerpc/44x: Support OCM(On Chip Memory) for APM821xx
> > SoC and Bluestone board
Such a CC list won't get you any good will. Send it only to the relevant
mailing lists with possibly the -one- concerned maintainer on CC. I
doubt Dave Miller or Matt Porter give any damn about those patches.
As for why it wasn't reviewed yet, well, reviewers are a finite resource
with limited time dedicated to it. If the patch is properly formed and
was posted to the linuxppc-dev@ozlabs.org, it should be tracked on
patchwork.ozlabs.org and won't be lost. Double check it's there (if it's
not, then the patch was probably corrupt).
Cheers,
Ben.
next prev parent reply other threads:[~2012-06-13 0:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 3:52 [PATCH] powerpc/44x: Support OCM(On Chip Memory) for APM821xx SoC and Bluestone board Vinh Nguyen Huu Tuong
2012-06-12 10:26 ` Vinh Huu Tuong Nguyen
2012-06-13 0:40 ` Benjamin Herrenschmidt [this message]
2012-06-13 1:22 ` Josh Boyer
2012-06-14 17:47 ` Josh Boyer
2012-06-15 3:19 ` Vinh Huu Tuong Nguyen
-- strict thread matches above, loose matches on Subject: below --
2012-07-03 8:52 Vinh Nguyen Huu Tuong
2012-08-08 12:23 ` Josh Boyer
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=1339548038.9220.80.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=vhtnguyen@apm.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).