From: Jes Sorensen <jes@sgi.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, Hugh Dickins <hugh@veritas.com>,
Nick Piggin <nickpiggin@yahoo.com.au>,
bjorn_helgaas@hp.com, cotte@de.ibm.com
Subject: Re: [patch] msepc driver (requires do_no_pfn)
Date: Tue, 04 Apr 2006 13:13:39 +0200 [thread overview]
Message-ID: <443254E3.3010203@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0604032015380.18399@yvahk01.tjqt.qr>
Jan Engelhardt wrote:
>> +config MSPEC
>> + tristate " Memory special operations driver"
>
> The two blanks after " are not needed anymore with the new Kconfig
> from 2.6.x.
Hi Jan,
You're right. I updated my patch here, next version will have it right.
Lets see what happens to the nopfn stuff first.
Thanks,
Jes
next prev parent reply other threads:[~2006-04-04 11:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-03 11:34 [patch] msepc driver (requires do_no_pfn) Jes Sorensen
2006-04-03 18:16 ` Jan Engelhardt
2006-04-04 11:13 ` Jes Sorensen [this message]
2006-04-11 14:31 ` [patch] mspec " Jes Sorensen
2006-04-12 9:10 ` Jes Sorensen
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=443254E3.3010203@sgi.com \
--to=jes@sgi.com \
--cc=akpm@osdl.org \
--cc=bjorn_helgaas@hp.com \
--cc=cotte@de.ibm.com \
--cc=hugh@veritas.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=torvalds@osdl.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 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).