From: Joe Perches <joe@perches.com>
To: David Daney <ddaney@caviumnetworks.com>
Cc: Ralf Baechle <ralf@linux-mips.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
linux-mips <linux-mips@linux-mips.org>
Subject: Re: [PATCH 00/24] MAINTAINERS: Add "Q" patchwork entries
Date: Thu, 14 Jan 2010 09:40:56 -0800 [thread overview]
Message-ID: <1263490856.1903.14.camel@Joe-Laptop.home> (raw)
In-Reply-To: <4B4F534B.5050007@caviumnetworks.com>
On Thu, 2010-01-14 at 09:24 -0800, David Daney wrote:
> I wonder if the MIPS patchwork site should also be included:
> http://patchwork.linux-mips.org/project/linux-mips/list/
Thanks. I think it should.
If Andrew accepts the series, I'll add a patch
if you don't first.
cheers,
prev parent reply other threads:[~2010-01-14 17:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1263452908.git.joe@perches.com>
2010-01-14 17:24 ` [PATCH 00/24] MAINTAINERS: Add "Q" patchwork entries David Daney
2010-01-14 17:40 ` Joe Perches [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=1263490856.1903.14.camel@Joe-Laptop.home \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=ddaney@caviumnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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