From: Ralf Baechle <ralf@linux-mips.org>
To: girish <girishvg@gmail.com>
Cc: Atsushi Nemoto <anemo@mba.ocn.ne.jp>,
"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>
Subject: Re: PATCH] cleanup hardcoding __pa/__va macros etc. (take-4)
Date: Fri, 29 Sep 2006 00:29:56 +0100 [thread overview]
Message-ID: <20060928232956.GE3394@linux-mips.org> (raw)
In-Reply-To: <C140DCAC.7A1C%girishvg@gmail.com>
On Thu, Sep 28, 2006 at 01:58:02AM +0900, girish wrote:
> Date: Thu, 28 Sep 2006 01:58:02 +0900
> Subject: PATCH] cleanup hardcoding __pa/__va macros etc. (take-4)
> From: girish <girishvg@gmail.com>
> To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
> CC: "linux-mips@linux-mips.org" <linux-mips@linux-mips.org>,
> girish <girishvg@gmail.com>
> Content-type: multipart/mixed;
> boundary="B_3242253489_7379959"
>
>
> > Using just plain text and adding Signed-off-by line would be preferred.
> > Also your patch seems against neither latest lmo nor kernel.org tree...
>
> The kernel sources I was referring to were 2.6.17-rc6.
>
>
> >> In the meantime, I couldn't find the changes suggested for SPARSEMEM support
> >> in the main source tree. Especially the ones reviewed during month of August
> >> ([PATCH] do not count pages in holes with sparsemem ...). Could you please
> >> resend the consolidated patch to the list? Thanks.
> >
> > August? I sent the patch with that title in July and applied already.
> >
> > http://www.linux-mips.org/git?p=linux.git;a=commit;h=239367b4
>
> Again, I was referring to older sources, that is 2.6.17-rc6. I have just
> upgraded reference sources to 2.6.18 as mentioned above & now I see the
> changes. Thanks. In fact I am experimenting on highmem/sparsemem with
> 2.6.16.16 kernel sources.
>
>
> Please find attached patch created from 2.6.18 (kernel.org) tree. Let me
> know if this is alright.
>
> Signed-off-by: Girish V. Gulawani <girishvg@gmail.com>
-#ifdef CONFIG_ISA
- if (low < max_dma)
+ if (low < max_dma) }
This doesn't quite compile.
Ralf
next prev parent reply other threads:[~2006-09-28 23:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-24 5:39 [PATCH] cleanup hardcoding __pa/__va macros etc girish
2006-09-24 7:15 ` [PATCH] cleanup hardcoding __pa/__va macros etc. (FWD) girish
2006-09-24 15:26 ` [PATCH] cleanup hardcoding __pa/__va macros etc Atsushi Nemoto
2006-09-25 14:51 ` [PATCH] cleanup hardcoding __pa/__va macros etc. (take-2) girish
2006-09-25 15:43 ` Atsushi Nemoto
[not found] ` <C13EBDF2.724C%girishvg@gmail.com>
2006-09-26 2:24 ` FW: " girish
2006-09-26 9:02 ` Atsushi Nemoto
2006-09-26 15:20 ` girish
2006-09-26 16:35 ` Atsushi Nemoto
2006-09-26 22:06 ` girish
2006-09-27 15:35 ` Atsushi Nemoto
2006-09-27 16:58 ` PATCH] cleanup hardcoding __pa/__va macros etc. (take-4) girish
2006-09-28 23:29 ` Ralf Baechle [this message]
2006-09-29 14:45 ` PATCH] cleanup hardcoding __pa/__va macros etc. (take-5) girish
2006-09-29 17:59 ` Atsushi Nemoto
2006-09-29 18:33 ` girish
2006-10-01 14:52 ` Atsushi Nemoto
2006-10-01 14:57 ` girish
2006-10-01 15:09 ` Atsushi Nemoto
2006-09-28 15:01 ` [PATCH] cleanup hardcoding __pa/__va macros etc. (take-2) Ralf Baechle
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=20060928232956.GE3394@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=anemo@mba.ocn.ne.jp \
--cc=girishvg@gmail.com \
--cc=linux-mips@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