From: "Pekka Enberg" <penberg@cs.helsinki.fi>
To: "Michael Halcrow" <mhalcrow@us.ibm.com>
Cc: "Andrew Morton" <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/5] eCryptfs: convert kmap() to kmap_atomic()
Date: Fri, 19 Jan 2007 14:04:47 +0200 [thread overview]
Message-ID: <84144f020701190404u5162db92mcea13a709d487602@mail.gmail.com> (raw)
In-Reply-To: <20070118212725.GD3643@us.ibm.com>
On 1/18/07, Michael Halcrow <mhalcrow@us.ibm.com> wrote:
> + page_data = (char *)kmap_atomic(page, KM_USER0);
> + lower_page_data = (char *)kmap_atomic(lower_page, KM_USER1);
Drop 'em redundant casts, please.
next prev parent reply other threads:[~2007-01-19 12:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 21:26 [PATCH 1/5] eCryptfs: convert f_op->write() to vfs_write() Michael Halcrow
2007-01-18 21:27 ` [PATCH 2/5] eCryptfs: convert kmap() to kmap_atomic() Michael Halcrow
2007-01-19 12:04 ` Pekka Enberg [this message]
2007-01-19 20:35 ` [PATCH 2/5 (try 2)] " Michael Halcrow
2007-01-18 21:28 ` [PATCH 3/5] eCryptfs: open-code flag checking and manipulation Michael Halcrow
2007-01-18 21:28 ` [PATCH 4/5] eCryptfs: add flush_dcache_page() calls Michael Halcrow
2007-01-18 21:29 ` [PATCH 5/5] eCryptfs: convert lookup_one_len() to lookup_one_len_nd() Michael Halcrow
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=84144f020701190404u5162db92mcea13a709d487602@mail.gmail.com \
--to=penberg@cs.helsinki.fi \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhalcrow@us.ibm.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®