From: jbarnes@sgi.com (Jesse Barnes)
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] more discontig fun
Date: Thu, 31 Jul 2003 20:28:57 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105968336018313@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105942849830042@msgid-missing>
On Thu, Jul 31, 2003 at 09:10:06AM -0700, jbarnes wrote:
> On Wed, Jul 30, 2003 at 05:32:50PM -0700, David Mosberger wrote:
> >
> > Jesse> On Wed, Jul 30, 2003 at 10:17:13AM -0700, Jesse Barnes wrote:
> > >> Ok, I'll fix this too. Thanks for looking at it.
> >
> > Jesse> Does this look better?
> >
> > Not really.
> >
> > Jesse> -efi_memmap_walk (efi_freemem_callback_t callback, void *arg)
> > Jesse> +efi_memmap_walk (efi_freemem_callback_t callback, void *arg, void *arg2)
> >
> > Why is this necessary? Why not just pack that extra argument into a
> > structure and pass the whole thing to "arg"?
>
> Duh. But now that I've gone through the exercise, it seems like the
> whole callback mechanism is a bit heavyweight (not to mention quite
> obtuse). But I guess that's another patch...
Now that I look at this, I'm not quite sure what you'd like. Would you
like all efi_memmap_walk calls to take a struct args with a function
pointer and argument or just filter_rsvd_memory? Or would you like to
see it cleaned up in some other way?
Thanks,
Jesse
next prev parent reply other threads:[~2003-07-31 20:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-28 21:35 [PATCH] more discontig fun Jesse Barnes
2003-07-30 17:17 ` Jesse Barnes
2003-07-30 23:32 ` Jesse Barnes
2003-07-30 23:53 ` Keith Owens
2003-07-30 23:56 ` Jesse Barnes
2003-07-31 0:32 ` David Mosberger
2003-07-31 20:28 ` Jesse Barnes [this message]
2003-08-04 23:27 ` David Mosberger
2003-08-04 23:30 ` Jesse Barnes
2003-09-08 18:31 ` Jesse Barnes
2003-09-08 18:41 ` Jesse Barnes
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=marc-linux-ia64-105968336018313@msgid-missing \
--to=jbarnes@sgi.com \
--cc=linux-ia64@vger.kernel.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