From: C Michael Sundius <Michael.sundius@sciatl.com>
To: Andy Whitcroft <apw@shadowen.org>,
Dave Hansen <dave@linux.vnet.ibm.com>,
linux-mm@kvack.org, linux-mips@linux-mips.org, "VomLehn,
David" <dvomlehn@cisco.com>,
me94043@yahoo.com
Subject: Re: Have ever checked in your mips sparsemem code into mips-linux tree?
Date: Mon, 06 Oct 2008 13:15:49 -0700 [thread overview]
Message-ID: <48EA71F5.1040200@sciatl.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 687 bytes --]
adding patch 2 containing Documentation:
- - - - - Cisco - - - - -
This e-mail and any attachments may contain information which is confidential,
proprietary, privileged or otherwise protected by law. The information is solely
intended for the named addressee (or a person responsible for delivering it to
the addressee). If you are not the intended recipient of this message, you are
not authorized to read, print, retain, copy or disseminate this message or any
part of it. If you have received this e-mail in error, please notify the sender
immediately by return e-mail and delete it from your computer.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0002-mips-sparsemem-howto.patch --]
[-- Type: text/x-patch; name="0002-mips-sparsemem-howto.patch", Size: 0 bytes --]
next reply other threads:[~2008-10-06 20:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-06 20:15 C Michael Sundius [this message]
2008-10-06 23:26 ` Have ever checked in your mips sparsemem code into mips-linux tree? Ralf Baechle
2008-10-07 0:33 ` John
-- strict thread matches above, loose matches on Subject: below --
2008-08-14 22:05 sparsemem support for mips with highmem C Michael Sundius
2008-08-14 22:35 ` Dave Hansen
2008-08-14 23:52 ` C Michael Sundius
2008-08-26 9:09 ` Andy Whitcroft
2008-10-06 20:15 ` Have ever checked in your mips sparsemem code into mips-linux tree? C Michael Sundius
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=48EA71F5.1040200@sciatl.com \
--to=michael.sundius@sciatl.com \
--cc=apw@shadowen.org \
--cc=dave@linux.vnet.ibm.com \
--cc=dvomlehn@cisco.com \
--cc=linux-mips@linux-mips.org \
--cc=linux-mm@kvack.org \
--cc=me94043@yahoo.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).