From: "Daniel Jacobowitz" <dan@debian.org>
To: <Administrator@vger.kernel.org>
Cc: <benh@kernel.crashing.org>, <linux-kernel@vger.kernel.org>,
<linuxppc-dev@lists.linuxppc.org>
Subject: Re: [PATCH 1/2] PPC32: New OCP core support
Date: Wed, 12 May 2004 04:15:56 +0100 [thread overview]
Message-ID: <000101c437cf$71227ca0$d100000a@sbs2003.local> (raw)
In-Reply-To: <000101c437c2$d7467ac0$d100000a@sbs2003.local>
On Wed, May 12, 2004 at 02:45:44AM +0100, Matt Porter wrote:
>
> On Tue, May 11, 2004 at 05:57:50PM -0700, Andrew Morton wrote:
> > Matt Porter <mporter@kernel.crashing.org> wrote:
> > >
> > > New OCP infrastructure ported from 2.4 along with several
> > > enhancements. Please apply.
> >
> > I only received patch 1/2.
> >
> > Could you please avoid using the same Subject: for different patches? It
> > confuses my auto-subject-to-patch-filename-munger and it's nice to more
> > specifically identify each patch anwyay.
>
> Oddly I sent unique subjects:
>
> Subject: [PATCH 1/2] PPC32: New OCP core support
> Subject: [PATCH 2/2] PPC32: PPC4xx updates for new OCP
>
> It appears 2/2 at least made it off my system to the remote mailer,
> will doublecheck.
Your mail is being duplicated by what looks like a broken news gateway,
or something similar, on linuxppc-dev:
Received: from host213-123-250-229.in-addr.btopenworld.com ([213.123.250.229]:15149
"EHLO 2003SERVER.sbs2003.local") by vger.kernel.org with ESMTP
id S264904AbUELBme (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
Tue, 11 May 2004 21:42:34 -0400
Received: from mail pickup service by 2003SERVER.sbs2003.local with Microsoft SMTPSVC;
Wed, 12 May 2004 02:45:44 +0100
>
> -Matt
>
>
>
>
--
Daniel Jacobowitz
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-05-12 3:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-12 0:01 [PATCH 1/2] PPC32: New OCP core support Matt Porter
2004-05-12 0:39 ` Valdis.Kletnieks
2004-05-12 1:01 ` Matt Porter
2004-05-12 1:10 ` Valdis.Kletnieks
2004-05-12 3:00 ` Valdis.Kletnieks
2004-05-12 13:32 ` Matt Porter
2004-05-12 3:15 ` Valdis.Kletnieks
2004-05-12 1:45 ` Matt Porter
2004-05-12 2:00 ` Matt Porter
2004-05-12 0:57 ` Andrew Morton
2004-05-12 1:06 ` Matt Porter
2004-05-12 1:45 ` Matt Porter
2004-05-12 2:38 ` Daniel Jacobowitz
2004-05-12 3:15 ` Daniel Jacobowitz [this message]
2004-05-12 1:30 ` Andrew Morton
2004-05-12 3:00 ` Valdis.Kletnieks
2004-05-12 3:15 ` Valdis.Kletnieks
2004-05-12 5:48 ` Christoph Hellwig
2004-05-12 6:15 ` Christoph Hellwig
2004-05-12 13:39 ` Matt Porter
2004-05-12 6:30 ` Christoph Hellwig
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='000101c437cf$71227ca0$d100000a@sbs2003.local' \
--to=dan@debian.org \
--cc=Administrator@vger.kernel.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.linuxppc.org \
/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