From: Andrew Morton <akpm@osdl.org>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: jim.houston@comcast.net, linux-arch@vger.kernel.org
Subject: Re: "[PATCH] idr.c: extra features enhancements" breaks some archs
Date: Tue, 20 Apr 2004 14:29:47 -0700 [thread overview]
Message-ID: <20040420142947.6501c5c4.akpm@osdl.org> (raw)
In-Reply-To: <200404202259.43931.bzolnier@elka.pw.edu.pl>
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl> wrote:
>
>
> http://linus.bkbits.net:8080/linux-2.5/cset@408422f91NJQZKJweeY7yvmNfDTRmg?nav=index.html|ChangeSet@-2d
>
> > [PATCH] idr.c: extra features enhancements
>
> This patch adds find_next_bit() call to lib/idr.c but find_next_bit()
> is not implemented on arm, arm26, cris, h8300, m68k, m68knommu, um and v850.
>
> Please fix it...
>
eww, how irritating.
find_next_bit() is used in:
- the cpumask code
- Andi's NUMA code
- drivers/atm/lanai.c
- the sched-domains patches in -mm
- and, now, lib/idr.c
the above architectures simply hadn't stumbled across it, but now they
have.
There are fairly generic-looking implementations of find_next_bit() in
alpha, parisc, others.
Could I please ask the relevant arch maintainers to prepare an implementation?
Thanks.
next parent reply other threads:[~2004-04-20 21:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200404202259.43931.bzolnier@elka.pw.edu.pl>
2004-04-20 21:29 ` Andrew Morton [this message]
2004-04-20 22:42 ` "[PATCH] idr.c: extra features enhancements" breaks some archs Russell King
2004-04-20 22:52 ` Bartlomiej Zolnierkiewicz
2004-04-20 23:14 ` Andrew Morton
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=20040420142947.6501c5c4.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=jim.houston@comcast.net \
--cc=linux-arch@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