From: Matthew Dobson <colpatch@us.ibm.com>
To: Trivial Patch Monkey <trivial@rustcorp.com.au>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>, linux-kernel@vger.kernel.org
Subject: [TRIVIAL][PATCH] Fix comment in include/linux/gfp.h
Date: Mon, 16 Jun 2003 14:21:42 -0700 [thread overview]
Message-ID: <3EEE34E6.20709@us.ibm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 304 bytes --]
Hi all,
Small fix for a comment in gfp.h. A bit ago, a fix went in to make
GFP_ZONEMASK accurate (was 0xf, now 0x3). The patch fixed the
definition of GFP_ZONEMASK in include/linux/mmzone.h, but didn't fix
this comment. It's just a comment fix, so please ignore as appropriate! ;)
Cheers!
-Matt
[-- Attachment #2: GFP_ZONEMASK_comment_fix.patch --]
[-- Type: text/plain, Size: 387 bytes --]
--- linux-2.5.70-bk17/include/linux/gfp.h Mon May 26 18:00:26 2003
+++ linux-2.5.70-bk17/include/linux/gfp.h.fixed Mon Jun 16 11:48:03 2003
@@ -7,7 +7,7 @@
/*
* GFP bitmasks..
*/
-/* Zone modifiers in GFP_ZONEMASK (see linux/mmzone.h - low four bits) */
+/* Zone modifiers in GFP_ZONEMASK (see linux/mmzone.h - low two bits) */
#define __GFP_DMA 0x01
#define __GFP_HIGHMEM 0x02
reply other threads:[~2003-06-16 21:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3EEE34E6.20709@us.ibm.com \
--to=colpatch@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=trivial@rustcorp.com.au \
/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