public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Matthew Dobson <colpatch@us.ibm.com>
Cc: linux-kernel@vger.kernel.org,
	"Martin J. Bligh" <mbligh@aracnet.com>,
	Andrew Morton <akpm@digeo.com>,
	Christoph Hellwig <hch@infradead.org>,
	Paolo Zeppegno <zeppegno.paolo@seat.it>, Andi Kleen <ak@muc.de>,
	lse-tech <lse-tech@lists.sourceforge.net>
Subject: Re: [rfc][patch] Memory Binding Take 2 (0/1)
Date: Fri, 4 Apr 2003 14:34:21 +0100	[thread overview]
Message-ID: <20030404143421.C25147@infradead.org> (raw)
In-Reply-To: <3E8BCB96.6090908@us.ibm.com>; from colpatch@us.ibm.com on Wed, Apr 02, 2003 at 09:50:14PM -0800

On Wed, Apr 02, 2003 at 09:50:14PM -0800, Matthew Dobson wrote:
> Alrighty, let's give this another go...
> 
> This patch hasn't changed much.  Just added bitmap_t, typedef'd to 
> unsigned long * for passing around bitmaps without breaking the 
> abstraction.  I think it's good if we can keep the underlying data type 
> hidden to partially future-proof (protect? ;) the code.

Not a good idea.  Se_bit & co are defined to work on unsigned longs arrays.


      parent reply	other threads:[~2003-04-04 13:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-03  5:50 [rfc][patch] Memory Binding Take 2 (0/1) Matthew Dobson
2003-04-03  5:56 ` [rfc][patch] Memory Binding Take 2 (1/1) Matthew Dobson
2003-04-03  6:37   ` Andrew Morton
2003-04-03 23:30     ` Matthew Dobson
2003-04-03 12:20   ` Hugh Dickins
2003-04-03 13:25     ` Paolo Zeppegno
2003-04-03 23:57     ` Matthew Dobson
2003-04-04 13:40   ` Christoph Hellwig
2003-04-04 13:34 ` Christoph Hellwig [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=20030404143421.C25147@infradead.org \
    --to=hch@infradead.org \
    --cc=ak@muc.de \
    --cc=akpm@digeo.com \
    --cc=colpatch@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lse-tech@lists.sourceforge.net \
    --cc=mbligh@aracnet.com \
    --cc=zeppegno.paolo@seat.it \
    /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