From: Jesse Barnes <jbarnes@engr.sgi.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>,
linux-mm <linux-mm@kvack.org>,
LSE <lse-tech@lists.sourceforge.net>,
Anton Blanchard <anton@samba.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
davidm@hpl.hp.com, tony.luck@intel.com
Subject: Re: [PATCH] don't pass mem_map into init functions
Date: Wed, 28 Jul 2004 18:33:55 -0700 [thread overview]
Message-ID: <200407281833.55574.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <1091056702.2871.617.camel@nighthawk>
On Wednesday, July 28, 2004 4:18 pm, Dave Hansen wrote:
> On Wed, 2004-07-28 at 15:39, Jesse Barnes wrote:
> > You're missing this little bit from your patchset. Cc'ing Tony and
> > David.
>
> Thanks for finding that. That appears to be an ia64-ism, so I think the
> rest of the patch is OK.
Well, it booted anyway :). I didn't check to see if any other arches had
their own memmap_init routines though, I'm assuming you already covered
those.
Jesse
WARNING: multiple messages have this Message-ID (diff)
From: Jesse Barnes <jbarnes@engr.sgi.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>,
linux-mm <linux-mm@kvack.org>,
LSE <lse-tech@lists.sourceforge.net>,
Anton Blanchard <anton@samba.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
davidm@hpl.hp.com, tony.luck@intel.com
Subject: Re: [PATCH] don't pass mem_map into init functions
Date: Wed, 28 Jul 2004 18:33:55 -0700 [thread overview]
Message-ID: <200407281833.55574.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <1091056702.2871.617.camel@nighthawk>
On Wednesday, July 28, 2004 4:18 pm, Dave Hansen wrote:
> On Wed, 2004-07-28 at 15:39, Jesse Barnes wrote:
> > You're missing this little bit from your patchset. Cc'ing Tony and
> > David.
>
> Thanks for finding that. That appears to be an ia64-ism, so I think the
> rest of the patch is OK.
Well, it booted anyway :). I didn't check to see if any other arches had
their own memmap_init routines though, I'm assuming you already covered
those.
Jesse
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-07-29 1:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-28 20:55 [PATCH] don't pass mem_map into init functions Dave Hansen
2004-07-28 21:58 ` Jesse Barnes
2004-07-28 21:58 ` Jesse Barnes
2004-07-28 22:01 ` Jesse Barnes
2004-07-28 22:01 ` Jesse Barnes
2004-07-28 22:19 ` Dave Hansen
2004-07-28 22:39 ` Jesse Barnes
2004-07-28 23:18 ` Dave Hansen
2004-07-28 23:18 ` Dave Hansen
2004-07-29 1:33 ` Jesse Barnes [this message]
2004-07-29 1:33 ` Jesse Barnes
2004-07-29 23:10 ` Dave Hansen
2004-07-29 23:10 ` Dave Hansen
2004-07-30 14:29 ` Martin J. Bligh
2004-07-30 14:29 ` Martin J. Bligh
-- strict thread matches above, loose matches on Subject: below --
2004-08-04 1:01 Dave Hansen
2004-08-04 18:48 ` Jesse Barnes
2004-08-05 4:42 ` Andrew Morton
2004-08-05 18:55 ` Dave Hansen
2004-08-05 21:13 ` Andrew Morton
2004-08-05 23:58 ` Dave Hansen
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=200407281833.55574.jbarnes@engr.sgi.com \
--to=jbarnes@engr.sgi.com \
--cc=anton@samba.org \
--cc=davidm@hpl.hp.com \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=mbligh@aracnet.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.