public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nate Diller <nate.diller@gmail.com>
To: Andrew Morton <akpm@osdl.org>, Alexander Viro <viro@zeniv.linux.org.uk>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [PATCH 13/13] fs: deprecate memclear_highpage_flush
Date: Tue, 10 Apr 2007 20:36:00 -0700	[thread overview]
Message-ID: <20070411033600.11000.89714.patchbomb.py@localhost> (raw)
In-Reply-To: <20070411033600.11000.38285.patchbomb.py@localhost>

Now that all the in-tree users are converted over to zero_user_page(),
deprecate the old memclear_highpage_flush() call.

Signed-off-by: Nate Diller <nate.diller@gmail.com>

---

diff -urpN -X dontdiff linux-2.6.21-rc6-mm1/include/linux/highmem.h linux-2.6.21-rc6-mm1-test/include/linux/highmem.h
--- linux-2.6.21-rc6-mm1/include/linux/highmem.h	2007-04-10 18:32:41.000000000 -0700
+++ linux-2.6.21-rc6-mm1-test/include/linux/highmem.h	2007-04-10 19:40:14.000000000 -0700
@@ -149,6 +149,8 @@ static inline void zero_user_page(struct
 	kunmap_atomic(kaddr, KM_USER0);
 }
 
+static void memclear_highpage_flush(struct page *page, unsigned int offset,
+					unsigned int size) __deprecated;
 static inline void memclear_highpage_flush(struct page *page, unsigned int offset, unsigned int size)
 {
 	return zero_user_page(page, offset, size);

  parent reply	other threads:[~2007-04-11  3:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-11  3:36 [PATCH 1/13] fs: convert core functions to zero_user_page Nate Diller
2007-04-11  3:36 ` [PATCH 11/13] reiserfs: use zero_user_page Nate Diller
2007-04-11  3:36 ` [PATCH 9/13] ocfs2: " Nate Diller
2007-04-11  3:36 ` Nate Diller [this message]
2007-04-11  5:58   ` [PATCH 13/13] fs: deprecate memclear_highpage_flush Andrew Morton
2007-04-11  3:36 ` [PATCH 6/13] gfs2: use zero_user_page Nate Diller
2007-04-11  3:36 ` [PATCH 8/13] ntfs: " Nate Diller
2007-04-11  3:36 ` [PATCH 5/13] ext4: " Nate Diller
2007-04-11  4:14   ` Andreas Dilger
2007-04-11  3:36 ` [PATCH 2/13] affs: " Nate Diller
2007-04-11  3:36 ` [PATCH 7/13] nfs: " Nate Diller
2007-04-11  3:36 ` [PATCH 3/13] ecryptfs: " Nate Diller
2007-04-11  3:36 ` [PATCH 4/13] ext3: " Nate Diller
2007-04-11  3:36 ` [PATCH 10/13] reiser4: " Nate Diller
2007-04-11  3:36 ` [PATCH 12/13] xfs: " Nate Diller
2007-04-11  5:56 ` [PATCH 1/13] fs: convert core functions to zero_user_page Andrew Morton
2007-04-11  6:14   ` Nate Diller
2007-04-11 14:54   ` Jörn Engel

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=20070411033600.11000.89714.patchbomb.py@localhost \
    --to=nate.diller@gmail.com \
    --cc=akpm@osdl.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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