From: "David S. Miller" <davem@redhat.com>
To: rusty@rustcorp.com.au
Cc: mingo@elte.hu, torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] streq()
Date: Mon, 23 Sep 2002 23:24:13 -0700 (PDT) [thread overview]
Message-ID: <20020923.232413.08022213.davem@redhat.com> (raw)
In-Reply-To: <20020924061722.688A32C0A6@lists.samba.org>
From: Rusty Russell <rusty@rustcorp.com.au>
Date: Tue, 24 Sep 2002 16:04:33 +1000
For runtime checks (which are never as good) you could change the GFP_
defined to set the high bit.
Another idea is to make a gfp_flags_t, that worked very well
for things like mm_segment_t.
next prev parent reply other threads:[~2002-09-24 6:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-24 4:49 [PATCH] streq() Rusty Russell
2002-09-24 5:40 ` Ingo Molnar
2002-09-24 6:04 ` Rusty Russell
2002-09-24 6:24 ` David S. Miller [this message]
2002-09-24 7:28 ` Rusty Russell
2002-09-24 7:38 ` Ingo Molnar
2002-09-24 8:19 ` David S. Miller
2002-09-24 13:07 ` Denis Vlasenko
2002-09-24 17:21 ` H. Peter Anvin
2002-09-25 11:27 ` Daniel Egger
2002-09-25 11:45 ` Russell King
2002-09-25 12:38 ` Daniel Egger
2002-09-25 12:19 ` Michael Sinz
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=20020923.232413.08022213.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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;
as well as URLs for NNTP newsgroup(s).