From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Matthew Dobson <colpatch@us.ibm.com>
Cc: linux-kernel@vger.kernel.org,
Linux Memory Management <linux-mm@kvack.org>,
"Bligh, Martin J." <mbligh@aracnet.com>
Subject: Re: Bug in __alloc_pages()?
Date: Sat, 19 Mar 2005 10:25:39 +1100 [thread overview]
Message-ID: <423B6373.8030107@yahoo.com.au> (raw)
In-Reply-To: <423B52FE.6030101@us.ibm.com>
Matthew Dobson wrote:
>
> Agreed. It seems unlikely, but not entirely impossible. All it would
> take is one sloppily coded driver, right? How about this patch instead?
>
Sure that would be fine with me. It kind of makes the logic
explicit, as Martin said.
Nick
WARNING: multiple messages have this Message-ID (diff)
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Matthew Dobson <colpatch@us.ibm.com>
Cc: linux-kernel@vger.kernel.org,
Linux Memory Management <linux-mm@kvack.org>,
"Bligh, Martin J." <mbligh@aracnet.com>
Subject: Re: Bug in __alloc_pages()?
Date: Sat, 19 Mar 2005 10:25:39 +1100 [thread overview]
Message-ID: <423B6373.8030107@yahoo.com.au> (raw)
In-Reply-To: <423B52FE.6030101@us.ibm.com>
Matthew Dobson wrote:
>
> Agreed. It seems unlikely, but not entirely impossible. All it would
> take is one sloppily coded driver, right? How about this patch instead?
>
Sure that would be fine with me. It kind of makes the logic
explicit, as Martin said.
Nick
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2005-03-18 23:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-17 0:39 Bug in __alloc_pages()? Matthew Dobson
2005-03-17 1:09 ` Nick Piggin
2005-03-17 1:09 ` Nick Piggin
2005-03-18 22:15 ` Matthew Dobson
2005-03-18 23:25 ` Nick Piggin [this message]
2005-03-18 23:25 ` Nick Piggin
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=423B6373.8030107@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=colpatch@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mbligh@aracnet.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 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.