linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jan Kara <jack@suse.cz>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Reiserfs & ext3 changes for 3.16-rc1
Date: Wed, 11 Jun 2014 19:37:30 +0200	[thread overview]
Message-ID: <20140611173730.GA9511@quack.suse.cz> (raw)
In-Reply-To: <CA+55aFzPvSGCorqEKRi87oCOrZN5RbUA1uUWq26WR=ZS2pNt+w@mail.gmail.com>

On Sat 07-06-14 16:52:49, Linus Torvalds wrote:
> On Wed, Jun 4, 2014 at 1:27 PM, Jan Kara <jack@suse.cz> wrote:
> >   Hello Linus,
> >
> >   could you please pull from
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git for_linus
> >
> > to get big reiserfs cleanup from Jeff, an ext3 deadlock fix, and some small
> > cleanups.
> 
> This does not work at all for me:
> 
>   fs/reiserfs/do_balan.c: In function ‘balance_leaf_new_nodes’:
>   fs/reiserfs/do_balan.c:1248:3: error: implicit declaration of
> function ‘format_bh’ [-Werror=implicit-function-declaration]
>      RFALSE(!buffer_journaled(tb->S_new[i])
>      ^
> 
> Hmm? "format_bh()"?
  Bah, so I screwed up and apparently didn't push out my for_next branch
after merging patches from Jeff so various build bots didn't catch the
problem and I only compiled kernels without CONFIG_REISERFS_DEBUG_CHECK so
I didn't see the problem either. Anyway, I've added commit fixing this to
my for_next & for_linus branches (things now compile fine) and I'll send
you new pull request. I'm sorry for the mess.

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

      parent reply	other threads:[~2014-06-11 17:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-04 20:27 [GIT PULL] Reiserfs & ext3 changes for 3.16-rc1 Jan Kara
2014-06-07 23:52 ` Linus Torvalds
2014-06-09 20:10   ` Jeff Mahoney
2014-06-11 17:37   ` Jan Kara [this message]

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=20140611173730.GA9511@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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).