From: Geert Uytterhoeven <geert@linux-m68k.org>
To: linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org,
linux-m68k@lists.linux-m68k.org
Cc: "David S. Miller" <davem@davemloft.net>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 0/4] resources: Add lookup_resource()
Date: Tue, 31 May 2011 09:47:15 +0200 [thread overview]
Message-ID: <BANLkTi=YE4fSVQTNaYAwZ1YijqsUfTRmHg@mail.gmail.com> (raw)
In-Reply-To: <1306006756-32009-1-git-send-email-geert@linux-m68k.org>
On Sat, May 21, 2011 at 21:39, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> The resource system is a nice existing subsystem to implement simple allocators
> on top of.
> Unfortunately, there's no official method to find an existing resource by a
> resource start address, which is needed for a freeing function that just takes
> the start address of the region to free.
>
> Currently there are 3 users of the resource subsystem that implement this by
> traversing the resource tree theirselves:
> - The Amiga Chip RAM allocator on m68k,
> - iomap()/iounmap() on sparc,
> - DMA allocation API on sparc.
> They all lack locking of the resource tree, as resource_lock is static in
> kernel/resource.c.
>
> Hence this patchset adds lookup_resource() and converts the above users to it.
>
> [1/4] sparc: _sparc_find_resource() should check for exact matches
> [2/4] resources: Add lookup_resource()
> [3/4] m68k/amiga: Chip RAM - Use lookup_resource()
> [4/4] sparc: iounmap() and *_free_coherent() - Use lookup_resource()
As I got two acks from David for the sparc bits and no objections, I
queued these
on my for-2.6.41 and for-next branches.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2011-05-31 7:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1306006756-32009-1-git-send-email-geert@linux-m68k.org>
2011-05-21 19:39 ` [PATCH 1/4] sparc: _sparc_find_resource() should check for exact matches Geert Uytterhoeven
2011-05-21 19:39 ` [PATCH 2/4] resources: Add lookup_resource() Geert Uytterhoeven
2011-05-21 19:39 ` [PATCH 3/4] m68k/amiga: Chip RAM - Use lookup_resource() Geert Uytterhoeven
2011-05-21 19:39 ` [PATCH 4/4] sparc: iounmap() and *_free_coherent() " Geert Uytterhoeven
2011-05-23 6:46 ` David Miller
[not found] ` <1306006756-32009-2-git-send-email-geert@linux-m68k.org>
2011-05-23 6:45 ` [PATCH 1/4] sparc: _sparc_find_resource() should check for exact matches David Miller
2011-05-31 7:47 ` Geert Uytterhoeven [this message]
2011-05-21 19:39 [PATCH 0/4] resources: Add lookup_resource() Geert Uytterhoeven
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='BANLkTi=YE4fSVQTNaYAwZ1YijqsUfTRmHg@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=sparclinux@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