public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Jan Kara <jack@suse.cz>,
	linux-kernel@vger.kernel.org, hch@infradead.org,
	reiserfs-devel@vger.kernel.org, jeffm@suse.com
Subject: Re: [PATCH] reiserfs: Truncate blocks not used by a write (v2)
Date: Thu, 8 Oct 2009 14:48:24 +0200	[thread overview]
Message-ID: <20091008124818.GB5073@nowhere> (raw)
In-Reply-To: <20090917115629.6f8f8f00.sfr@canb.auug.org.au>

On Thu, Sep 17, 2009 at 11:56:29AM +1000, Stephen Rothwell wrote:
> Hi Frederic,
> 
> On Thu, 17 Sep 2009 02:56:34 +0200 Frederic Weisbecker <fweisbec@gmail.com> wrote:
> >
> > Note that the kill-the-bkl/reiserfs tree has suffered from too much
> > lock inversion problems lately. Even though I just fixed the last one
> > reported, I would feel more comfortable to schedule this tree for .33
> > rather than .32
> > 
> > So this tree can be removed from -next and reintegrated once -rc1 is
> > released, without problem.
> 
> OK, I have removed it from today.  Please let me know when it should be
> readded (in case I forget - which at my age is likely :-)).


Hi Stephen,

Now that -rc1 has been released (well.. -rc2, or..hmm...), could you please
reintegrate the tree:

git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git
	reiserfs/kill-bkl

into -next ?

It is based on linux-2.6.31, I haven't merged 32-rc3 into
it because there is no conflict between those and there are no
dependencies against latest changes.

Tell me if you need something. It's possible there are pending
patches in reiserfs for .33 in -next which might conflict, I don't
know. But if you need help to fix the conflicts, just tell me.

Thanks!
	


  reply	other threads:[~2009-10-08 12:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-16 17:25 [PATCH] reiserfs: Truncate blocks not used by a write (v2) Jan Kara
2009-09-16 21:48 ` Andrew Morton
2009-09-17  0:56   ` Frederic Weisbecker
2009-09-17  1:56     ` Stephen Rothwell
2009-10-08 12:48       ` Frederic Weisbecker [this message]
2009-10-08 23:11         ` Stephen Rothwell

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=20091008124818.GB5073@nowhere \
    --to=fweisbec@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=hch@infradead.org \
    --cc=jack@suse.cz \
    --cc=jeffm@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiserfs-devel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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