public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Theodore Tso <tytso@mit.edu>,
	Christoph Hellwig <hch@infradead.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] ext4 bugfixes
Date: Thu, 24 Jul 2008 16:03:16 -0400	[thread overview]
Message-ID: <20080724200316.GA11862@infradead.org> (raw)
In-Reply-To: <20080715124652.GB16704@mit.edu>

On Tue, Jul 15, 2008 at 08:46:52AM -0400, Theodore Tso wrote:
> On Tue, Jul 15, 2008 at 12:37:18AM -0400, Christoph Hellwig wrote:
> > And for this one I haven't even heard back on my review comments.  None
> > of them is a merge blocker so it's not critical, but I find it quite odd
> > that the pull request is coming before even replying to the review
> > comments.
> 
> Can you resend your e-mail, please?  I can't seem to find it in my
> inbox.  Thanks!!

It was just a paragraph in the mail also commenting on the previously
core parts:

> Also the code still deals with the !buffer_mapped and no buffers on page
> cases all over which isn't needed anymore with ->page_mkwrite
> implemented.
> Similarly the !get_block case in mpage_da_writepages doesn't make any
> sense - it's never used and if people would want to use
> generic_writepages they could trivially just call it directly.

I've got a comment from Jan that the no buffers case can still happen,
so that can be removed.

Any chance you could also look into the kerneldoc comments for the newly
exported fs/mpage.c routines as commented on the updated patch?

  reply	other threads:[~2008-07-24 20:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-15  3:56 [GIT PULL] ext4 bugfixes Theodore Ts'o
2008-07-15  4:37 ` Christoph Hellwig
2008-07-15 12:46   ` Theodore Tso
2008-07-24 20:03     ` Christoph Hellwig [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-06-06 22:17 Theodore Ts'o

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=20080724200316.GA11862@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    /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