From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Linus Torvalds <torvalds@transmeta.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bitops cleanup 3/4
Date: Tue, 2 Apr 2002 23:08:47 -0700 [thread overview]
Message-ID: <200204030608.g3368l903461@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <E16sbI0-0005ug-00@wagner.rustcorp.com.au>
Rusty Russell writes:
> Linus, please apply (no object code changes).
>
> This changes everything arch specific PPC and i386 which should have
> been unsigned long (it doesn't *matter*, but bad habits get copied).
>
> I left the devfs ones for Richard to submit separately, since they
> actually change the resulting code.
??? But you didn't leave the devfs ones alone: your patch changes a
devfs file:
> diff -urN -I \$.*\$ --exclude TAGS -X /home/rusty/current-dontdiff --minimal linux-2.5.7-pre1/include/linux/devfs_fs_kernel.h working-2.5.7-pre1-bitops/include/linux/devfs_fs_kernel.h
> --- linux-2.5.7-pre1/include/linux/devfs_fs_kernel.h Fri Mar 15 15:37:39 2002
> +++ working-2.5.7-pre1-bitops/include/linux/devfs_fs_kernel.h Sat Mar 16 13:54:53 2002
> @@ -54,7 +54,7 @@
> unsigned char sem_initialised;
> unsigned int num_free; /* Num free in bits */
> unsigned int length; /* Array length in bytes */
> - __u32 *bits;
> + unsigned long *bits;
> struct semaphore semaphore;
> };
>
Anyway, I hope to have a devfs patch for 2.5.x ready before next
week. I've got some other changes in the works, as well as the bitops
changes, which I've already submitted for 2.4.x.
Regards,
Richard....
Permanent: rgooch@atnf.csiro.au
Current: rgooch@ras.ucalgary.ca
next prev parent reply other threads:[~2002-04-03 6:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-03 3:18 Rusty Russell
2002-04-03 6:08 ` Richard Gooch [this message]
2002-04-03 6:29 ` Rusty Russell
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=200204030608.g3368l903461@vindaloo.ras.ucalgary.ca \
--to=rgooch@ras.ucalgary.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--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
all inboxes | Powered by JetHome®