linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: linux-mm@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [Review request] Fix page_mkwrite() for blocksize < pagesize
Date: Sat, 6 Jun 2009 01:32:17 +0200	[thread overview]
Message-ID: <20090605233216.GE11650@duck.suse.cz> (raw)

  Hi,

  could someone have a look at a patch set I've posted a week or so ago
to LKML. It starts at:
http://lkml.org/lkml/2009/5/27/317
  Mainly, what I'd like to get opinions on is the third patch implementing
VFS helpers for easier handling of page_mkwrite() when blocksize <
pagesize. I'd like to get the patchset merged but before that I'd like to
get an agreement of people here that this is the way we want to go...
Thanks a lot for review in advance.

									Honza
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

             reply	other threads:[~2009-06-05 23:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-05 23:32 Jan Kara [this message]
2009-06-13  4:00 ` [Review request] Fix page_mkwrite() for blocksize < pagesize Theodore Tso
2009-06-15 18:06   ` Jan Kara

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=20090605233216.GE11650@duck.suse.cz \
    --to=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@vger.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 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).