From: Randy Dunlap <rdunlap@infradead.org>
To: "Raymond L. Rivera" <ray.l.rivera@gmail.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Jiri Kosina <trivial@kernel.org>
Subject: Re: [PATCH 2/2] linux/pagemap.h: Fixed a typo in a code comment.
Date: Fri, 25 Jul 2014 12:51:35 -0700 [thread overview]
Message-ID: <53D2B547.5080607@infradead.org> (raw)
In-Reply-To: <1406194785-19596-3-git-send-email-ray.l.rivera@gmail.com>
On 07/24/14 02:39, Raymond L. Rivera wrote:
> Corrected a minor typo in a code comment where 'be' was missing.
>
> Signed-off-by: Raymond L. Rivera <ray.l.rivera@gmail.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> include/linux/pagemap.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/pagemap.h b/include/linux/pagemap.h
> index 0a97b58..bcabdbe 100644
> --- a/include/linux/pagemap.h
> +++ b/include/linux/pagemap.h
> @@ -96,7 +96,7 @@ static inline void mapping_set_gfp_mask(struct address_space *m, gfp_t mask)
> }
>
> /*
> - * The page cache can done in larger chunks than
> + * The page cache can be done in larger chunks than
> * one page, because it allows for more efficient
> * throughput (it can then be mapped into user
> * space in smaller chunks for same flexibility).
>
--
~Randy
next prev parent reply other threads:[~2014-07-25 19:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 9:39 [PATCH 0/2] Minor documentation typo fixes Raymond L. Rivera
2014-07-24 9:39 ` [PATCH 1/2] CodingStyle: Fixed a minor typo Raymond L. Rivera
2014-07-25 19:51 ` Randy Dunlap
2014-07-24 9:39 ` [PATCH 2/2] linux/pagemap.h: Fixed a typo in a code comment Raymond L. Rivera
2014-07-25 19:51 ` Randy Dunlap [this message]
2014-07-25 19:50 ` [PATCH 0/2] Minor documentation typo fixes Randy Dunlap
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=53D2B547.5080607@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ray.l.rivera@gmail.com \
--cc=trivial@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.