From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: paulus@samba.org
Cc: Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org, dhinds@zen.stanford.edu
Subject: Re: Memory region check in drivers/pcmcia/rsrc_mgr.c
Date: Sun, 08 Jul 2001 12:36:50 -0400 [thread overview]
Message-ID: <3B488C22.16F127E9@mandrakesoft.com> (raw)
In-Reply-To: <15174.62880.772230.734585@tango.paulus.ozlabs.org> <Pine.LNX.4.33.0107071103070.31249-100000@penguin.transmeta.com> <15176.6825.508736.915376@tango.paulus.ozlabs.org>
Paul Mackerras wrote:
> +static struct resource *resource_parent(unsigned long b, unsigned long n,
> + int flags, socket_info_t *s)
> +static inline int check_io_resource(unsigned long b, unsigned long n,
> + socket_info_t *s)
> +static inline int check_mem_resource(unsigned long b, unsigned long n,
> + socket_info_t *s)
> +static struct resource *make_resource(unsigned long b, unsigned long n,
> + int flags, char *name)
> +static int request_io_resource(unsigned long b, unsigned long n,
> + char *name, socket_info_t *s)
> +static int request_mem_resource(unsigned long b, unsigned long n,
> + char *name, socket_info_t *s)
patch looks ok. I wonder if this stuff is useful to other users?
resource_parent appears to be the only actual user of socket_info_t
data. Since resource_parent only uses one datum out of all of
socket_info_t, you could reasonably eliminate this code's dependency on
socket_info_t.
--
Jeff Garzik | A recent study has shown that too much soup
Building 1024 | can cause malaise in laboratory mice.
MandrakeSoft |
prev parent reply other threads:[~2001-07-08 16:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-07 11:42 Memory region check in drivers/pcmcia/rsrc_mgr.c Paul Mackerras
2001-07-07 11:51 ` Jeff Garzik
2001-07-07 18:13 ` Linus Torvalds
2001-07-08 8:32 ` Paul Mackerras
2001-07-08 16:36 ` Jeff Garzik [this message]
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=3B488C22.16F127E9@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=dhinds@zen.stanford.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=torvalds@transmeta.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