From: Nick Piggin <npiggin@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org,
Mark Fasheh <mark.fasheh@oracle.com>,
Linux Memory Management <linux-mm@kvack.org>
Subject: Re: [patch 12/41] fs: introduce write_begin, write_end, and perform_write aops
Date: Thu, 31 May 2007 07:15:39 +0200 [thread overview]
Message-ID: <20070531051539.GK20107@wotan.suse.de> (raw)
In-Reply-To: <20070530221121.7eadc807.akpm@linux-foundation.org>
On Wed, May 30, 2007 at 10:11:21PM -0700, Andrew Morton wrote:
> On Thu, 31 May 2007 06:57:54 +0200 Nick Piggin <npiggin@suse.de> wrote:
>
> > > Don't know - I shelved the patches.
> >
> > Oh, that didn't last long :P
>
> I have a heap of other stuff to get out the door. If I have to
> do just two bisects then it's 4AM and I give up then I have to repull
> everything and we're back to square one.
>
> Fortunately, I didn't need to do a bisect this time. That's unusual.
>
> >
> > > Given the great pile of build errors, I think we need the next rev.
> >
> > I was working on bringing some of the others uptodate (hopefully
> > before you did another release). There is not much point in doing
> > that if they don't get merged because the patches just break again.
>
> There's not much point in sending build-busting patches either. Lots
> of people run allmodconfig.
>
> My sympathy for broken patches is limited - you should see what happens
> over here ;)
>
> I can do you a rollup with those patches reinstated after I've done rc3-mm1
> if you like.
OK, if you are planning to get a release out now, that's fair
enough.
If you can send that rollup, it would be good. I could try getting
everything to compile and do some more testing on it too.
> > Were there build errors in any core code or converted filesystems?
> > AFAIKS it was just in reiser4 and a couple of the "cont" filesystems
> > that didn't get converted yet.
>
> The _cont filesystems, reiser4 and that revoke warning.
OK, thanks.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-05-31 5:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070524052844.860329000@suse.de>
2007-05-25 12:21 ` [patch 01/41] mm: revert KERNEL_DS buffered write optimisation npiggin
2007-05-25 12:21 ` [patch 02/41] Revert 81b0c8713385ce1b1b9058e916edcf9561ad76d6 npiggin, Andrew Morton
2007-05-25 12:21 ` [patch 03/41] Revert 6527c2bdf1f833cc18e8f42bd97973d583e4aa83 npiggin, Andrew Morton
2007-05-25 12:21 ` [patch 04/41] mm: clean up buffered write code npiggin, Andrew Morton
2007-05-25 12:21 ` [patch 05/41] mm: debug write deadlocks npiggin
2007-05-25 12:21 ` [patch 06/41] mm: trim more holes npiggin
2007-05-25 12:21 ` [patch 07/41] mm: buffered write cleanup npiggin
2007-05-25 12:21 ` [patch 08/41] mm: write iovec cleanup npiggin
2007-05-25 12:21 ` [patch 09/41] mm: fix pagecache write deadlocks npiggin
2007-05-25 12:21 ` [patch 10/41] mm: buffered write iterator npiggin
2007-05-25 12:21 ` [patch 11/41] fs: fix data-loss on error npiggin
2007-05-25 12:21 ` [patch 12/41] fs: introduce write_begin, write_end, and perform_write aops npiggin
2007-05-31 4:30 ` Andrew Morton
2007-05-31 4:43 ` Nick Piggin
2007-05-31 4:52 ` Andrew Morton
2007-05-31 4:57 ` Nick Piggin
2007-05-31 5:11 ` Andrew Morton
2007-05-31 5:15 ` Nick Piggin [this message]
2007-05-31 7:05 ` Andrew Morton
2007-06-01 1:18 ` Nick Piggin
2007-05-25 12:21 ` [patch 13/41] mm: restore KERNEL_DS optimisations npiggin
[not found] <20070514060619.689648000@wotan.suse.de>
2007-05-14 6:06 ` [patch 12/41] fs: introduce write_begin, write_end, and perform_write aops npiggin
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=20070531051539.GK20107@wotan.suse.de \
--to=npiggin@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mark.fasheh@oracle.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