From: Matt Porter <mporter@kernel.crashing.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Matt Porter <mporter@kernel.crashing.org>,
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: Tue, 11 May 2004 18:06:56 -0700 [thread overview]
Message-ID: <20040511180656.B4901@home.com> (raw)
In-Reply-To: <20040511175750.12bad316.akpm@osdl.org>; from akpm@osdl.org on Tue, May 11, 2004 at 05:57:50PM -0700
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.
-Matt
next prev parent reply other threads:[~2004-05-12 1:22 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 [this message]
2004-05-12 1:45 ` Matt Porter
2004-05-12 2:38 ` Daniel Jacobowitz
2004-05-12 3:15 ` Daniel Jacobowitz
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=20040511180656.B4901@home.com \
--to=mporter@kernel.crashing.org \
--cc=akpm@osdl.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