All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: unlisted-recipients:; (no To-header on input)
Cc: torvalds@osdl.org, akpm@osdl.org, davidm@snapgear.com,
	linux-kernel@vger.kernel.org, uclinux-dev@uclinux.org
Subject: Re: [PATCH] Bit operations
Date: Thu, 11 Nov 2004 12:49:09 +0000	[thread overview]
Message-ID: <29033.1100177349@redhat.com> (raw)
In-Reply-To: <200411081432.iA8EWfnc023411@warthog.cambridge.redhat.com>


Hi Andrew,

> The attached patch provides an out-of-line implementation of find_next_bit()
> and rearranges linux/bitops.h to avoid a dependency loop between inline
> functions in there and in asm/bitops.h trying to include one another.

Is there any reason you dropped the part of this patch that rearranged
linux/bitops.h? asm/bitops.h may need generic_ffs() for implementing
sched_find_first_bit(), and obviously asm/bitops.h can't include
linux/bitops.h.

David

  reply	other threads:[~2004-11-11 12:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-08 14:32 [PATCH] Bit operations dhowells
2004-11-11 12:49 ` David Howells [this message]
2004-11-11 20:32   ` 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=29033.1100177349@redhat.com \
    --to=dhowells@redhat.com \
    --cc=akpm@osdl.org \
    --cc=davidm@snapgear.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    --cc=uclinux-dev@uclinux.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 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.