From: Dean Nelson <dcn@sgi.com>
To: jes@sgi.com, tony.luck@intel.com, linux-kernel@vger.kernel.org,
linux-ia64@vger.kernel.org
Subject: Re: [Patch 0/5] prepare XPC and XPNET to support SGI UV
Date: Tue, 25 Mar 2008 15:14:23 -0500 [thread overview]
Message-ID: <20080325201423.GB4446@sgi.com> (raw)
In-Reply-To: <20080325192524.343385569@attica.americas.sgi.com>
On Tue, Mar 25, 2008 at 02:25:24PM -0500, dcn@sgi.com wrote:
> This set of five patches moves XPC and XPNET to drivers/misc/xp in preparation
> for enabling X86_64 support.
It looks like the 2nd patch of this set has been blocked from the mailing
list because of its size. At least that's my assumption. The size of the
five patches are as follows (listed in patch order):
-rw-r--r-- 1 dcn os1 4880 2008-03-25 14:05 uncached-pages
-rw-r--r-- 1 dcn os1 471050 2008-03-25 14:10 move-xp
-rw-r--r-- 1 dcn os1 203046 2008-03-25 14:14 generic-xp
-rw-r--r-- 1 dcn os1 163868 2008-03-25 14:17 Lindent
-rw-r--r-- 1 dcn os1 49723 2008-03-25 14:46 checkpatch.pl
The missing patch moved XPC and XPNET from arch/ia64/sn to drivers/misc/xp.
How should such a patch be submitted?
Thanks,
Dean
next prev parent reply other threads:[~2008-03-25 20:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-25 19:25 [Patch 0/5] prepare XPC and XPNET to support SGI UV dcn
2008-03-25 19:25 ` [Patch 1/5] add multi-page allocation to the uncached allocator dcn
2008-03-25 19:25 ` [Patch 3/5] prepare XPC and XPNET for future support of SGIs UV architecture dcn
2008-03-25 19:25 ` [Patch 4/5] run drivers/misc/xp through scripts/Lindent dcn
2008-03-25 19:25 ` [Patch 5/5] run drivers/misc/xp through scripts/checkpatch.pl dcn
2008-03-25 20:05 ` Dean Nelson
2008-03-26 10:03 ` Andy Whitcroft
2008-03-26 16:58 ` Dean Nelson
2008-03-25 20:14 ` Dean Nelson [this message]
2008-03-25 22:49 ` [Patch 0/5] prepare XPC and XPNET to support SGI UV Luck, Tony
2008-03-25 23:04 ` Andreas Schwab
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=20080325201423.GB4446@sgi.com \
--to=dcn@sgi.com \
--cc=jes@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.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