From: Richard Henderson <rth@twiddle.net>
To: David Howells <dhowells@redhat.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Roman Zippel <zippel@linux-m68k.org>,
Jeff Garzik <jgarzik@mandrakesoft.com>,
davidm@hpl.hp.com, "David S. Miller" <davem@redhat.com>,
anton@samba.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] move task_struct allocation to arch
Date: Fri, 15 Feb 2002 13:56:22 -0800 [thread overview]
Message-ID: <20020215135622.B25047@twiddle.net> (raw)
In-Reply-To: <zippel@linux-m68k.org> <23760.1013782075@warthog.cambridge.redhat.com>
In-Reply-To: <23760.1013782075@warthog.cambridge.redhat.com>; from dhowells@redhat.com on Fri, Feb 15, 2002 at 02:07:55PM +0000
On Fri, Feb 15, 2002 at 02:07:55PM +0000, David Howells wrote:
> Should I move the convenience bit operations back to the arch header, so that
> the M68K guys can have byte-sized flags (which they can use TAS/TST on)?
If you provide some way to override the convenience bit operations,
then I suspect that you can let most folks use the byte ops. It's
only older alphas that would absolutely have to play games.
Of course, I now have 9 flag bits defined, so I might not go back
to bytes anyway...
r~
next prev parent reply other threads:[~2002-02-15 21:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-14 15:26 [PATCH] move task_struct allocation to arch David Howells
2002-02-14 16:13 ` Jeff Garzik
2002-02-14 16:32 ` David Howells
2002-02-14 16:46 ` Jeff Garzik
2002-02-14 17:03 ` David Howells
2002-02-14 20:48 ` Roman Zippel
2002-02-14 23:53 ` Richard Henderson
2002-02-15 9:56 ` Jeff Garzik
2002-02-15 10:01 ` Jeff Garzik
2002-02-15 11:25 ` Roman Zippel
2002-02-15 11:37 ` David Howells
2002-02-15 12:20 ` Roman Zippel
2002-02-15 12:56 ` David Howells
2002-02-15 13:49 ` Roman Zippel
2002-02-15 13:51 ` Jeff Garzik
2002-02-15 14:22 ` Roman Zippel
2002-02-15 14:07 ` David Howells
2002-02-15 14:28 ` Roman Zippel
2002-02-15 21:56 ` Richard Henderson [this message]
2002-02-15 21:52 ` Richard Henderson
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=20020215135622.B25047@twiddle.net \
--to=rth@twiddle.net \
--cc=anton@samba.org \
--cc=davem@redhat.com \
--cc=davidm@hpl.hp.com \
--cc=dhowells@redhat.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=zippel@linux-m68k.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.