linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: C Michael Sundius <Michael.sundius@sciatl.com>
To: Andy Whitcroft <apw@shadowen.org>
Cc: Dave Hansen <dave@linux.vnet.ibm.com>,
	linux-mm@kvack.org, linux-mips@linux-mips.org, me94043@yahoo.com,
	"VomLehn, David" <dvomlehn@cisco.com>
Subject: Re: Have ever checked in your mips sparsemem code into mips-linux tree?
Date: Mon, 06 Oct 2008 13:15:44 -0700	[thread overview]
Message-ID: <48EA71F0.3060003@sciatl.com> (raw)
In-Reply-To: <20080826090936.GC29207@brain>

[-- Attachment #1: Type: text/plain, Size: 2001 bytes --]

John wrote:


> Hi Michael,
>
> After I read this link, noticed that you have the following patch, but when I check up the mips-linux, the patch is not there.
>
> I wonder if you could explain to me a little bit?
>
> Thank you!
>
> John
> P.S.: I also worked at SciAtl a few years ago in IPTV division.
>   
John,

I *think* I got tentative signoff from Dave and Any below as per the 
copied snipits below.
I made the modifications that they suggested. please see the attached 
for two patches:
a) the code
b) the sparsemem.txt doc

not sure if the mips powers that be were ok w/ it. pardon my ignorance, 
not sure if I am
required to do anymore. There was some comment to try this out w/ the 
CONFIG_SPARSEMEM_VMEMMAP
which I believe should "just work", but we've never tried it as of yet, 
so by my rule I can't
say it is so.. (has anyone tried that?)

Mike

====================================================


Dave Hansen wrote:

Looks great to me.  I can't test it, of course, but I don't see any
problems with it.

Signed-off-by: Dave Hansen <dave@linux.vnet.ibm.com>

-- Dave


Andy Whitcroft wrote:
>
>
> Otherwise it looks good to me.  I see from the rest of the thread that
> there is some discussion over the sizes of these, with that sorted.
>
> Acked-by: Andy Whitcroft <apw@shadowen.org>
>
> -apw
>   
adding patch 1 containing code only:





     - - - - -                              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: 0001-mips-sparsemem-support.patch --]
[-- Type: text/x-patch; name="0001-mips-sparsemem-support.patch", Size: 0 bytes --]



  reply	other threads:[~2008-10-06 20:15 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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:16   ` C Michael Sundius
2008-08-14 23:52   ` C Michael Sundius
2008-08-15  0:02     ` Dave Hansen
2008-08-15  8:03     ` Thomas Bogendoerfer
2008-08-15 15:48       ` Dave Hansen
2008-08-15 16:12         ` C Michael Sundius
2008-08-15 16:20           ` Dave Hansen
2008-08-15 16:33           ` Thomas Bogendoerfer
2008-08-15 17:16             ` C Michael Sundius
2008-08-15 17:37               ` Dave Hansen
2008-08-15 18:17                 ` C Michael Sundius
2008-08-15 18:23                   ` Dave Hansen
2008-08-16 20:07                     ` Thomas Bogendoerfer
2008-08-18 16:44                   ` Randy Dunlap
2008-08-18 21:24                     ` Christoph Lameter
2008-08-18 21:27                       ` Dave Hansen
2008-08-18 21:33                         ` Christoph Lameter
2009-01-16 21:46                           ` Michael Sundius
2009-01-21 14:39                             ` Christoph Lameter
2008-08-18 21:57                       ` David VomLehn
2008-08-19 13:06                         ` Christoph Lameter
2008-08-19 23:38                           ` David VomLehn
2008-08-19 23:53                             ` Jon Fraser
2008-08-20 13:58                             ` Christoph Lameter
2008-08-20 19:28                               ` David VomLehn
2008-08-20 20:51                                 ` Christoph Lameter
2008-08-15 16:30         ` Thomas Bogendoerfer
2008-08-26  9:09     ` Andy Whitcroft
2008-10-06 20:15       ` C Michael Sundius [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-10-06 20:15 Have ever checked in your mips sparsemem code into mips-linux tree? C Michael Sundius
2008-10-06 23:26 ` Ralf Baechle
2008-10-07  0:33 ` John

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=48EA71F0.3060003@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).