From: Anton Blanchard <anton@samba.org>
To: Andi Kleen <ak@suse.de>
Cc: Arjan van de Ven <arjan@infradead.org>,
linux-kernel@vger.kernel.org, jbeulich@novell.com
Subject: Re: [PATCH] adjust /dev/{kmem,mem,port} write handlers
Date: Mon, 6 Mar 2006 11:11:08 +1100 [thread overview]
Message-ID: <20060306001108.GH5552@krispykreme> (raw)
In-Reply-To: <p738xrrd4l6.fsf@verdi.suse.de>
> If you mmap it doesn't make any sense to not have read/write.
> And they are sometimes quite useful for debugging.
Agreed, I use them quite a lot too.
Anton
next prev parent reply other threads:[~2006-03-06 2:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-03 9:31 [PATCH] adjust /dev/{kmem,mem,port} write handlers Jan Beulich
2006-03-03 9:38 ` Arjan van de Ven
2006-03-03 12:48 ` Robin Holt
2006-03-03 13:45 ` Andi Kleen
2006-03-06 0:11 ` Anton Blanchard [this message]
2006-03-05 6:15 ` Andrew Morton
2006-03-06 8:08 ` Jan Beulich
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=20060306001108.GH5552@krispykreme \
--to=anton@samba.org \
--cc=ak@suse.de \
--cc=arjan@infradead.org \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.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.