From: Randy Dunlap <rdunlap@xenotime.net>
To: Marco Stornelli <marco.stornelli@coritel.it>
Cc: mtk.manpages@gmail.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] documentation: xip documentation update
Date: Mon, 22 Sep 2008 08:30:50 -0700 [thread overview]
Message-ID: <20080922083050.3ec7b7e9.rdunlap@xenotime.net> (raw)
In-Reply-To: <48D76770.9000808@coritel.it>
On Mon, 22 Sep 2008 11:37:52 +0200 Marco Stornelli wrote:
> From: Marco Stornelli <marco.stornelli@gmail.com>
>
> xip documentation updated
> Signed-off-by: Marco Stornelli <marco.stornelli@gmail.com>
> ---
>
> --- linux-2.6.26.5/Documentation/filesystems/xip.txt.orig 2008-08-20 20:11:37.000000000 +0200
> +++ linux-2.6.26.5/Documentation/filesystems/xip.txt 2008-09-22 11:27:46.000000000 +0200
> @@ -39,10 +39,11 @@ The block device operation is optional,
> today:
> - dcssblk: s390 dcss block device driver
>
> -An address space operation named get_xip_page is used to retrieve reference
> -to a struct page. To address the target page, a reference to an address_space,
> -and a sector number is provided. A 3rd argument indicates whether the
> -function should allocate blocks if needed.
> +An address space operation named get_xip_mem is used to retrieve reference
> +to a page frame number and a kernel address. To obtain these values a reference
> +to an address_space is provided. This function is in charge to assign values to
How about:
This function assigns values to the kmem and
pfn parameters.
> +the pointers kmem and pfn. The 3rd argument indicates whether the function
> +should allocate blocks if needed.
>
> This address space operation is mutually exclusive with readpage&writepage that
> do page cache read/write operations.
Thanks.
---
~Randy
next prev parent reply other threads:[~2008-09-22 15:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-22 9:37 Marco Stornelli
2008-09-22 15:30 ` Randy Dunlap [this message]
2008-09-23 7:03 ` Marco Stornelli
2008-09-23 11:49 ` Marco Stornelli
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=20080922083050.3ec7b7e9.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.stornelli@coritel.it \
--cc=mtk.manpages@gmail.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
all inboxes | Powered by JetHome®