archive mirror
 help / color / mirror / Atom feed
From: Sedat Dilek <>
To: Stephen Rothwell <>, Jens Axboe <>
Cc:, LKML <>,
	Linus <>
Subject: Re: linux-next: Tree for Oct 25 (block ?)
Date: Tue, 25 Oct 2011 15:04:53 +0200	[thread overview]
Message-ID: <> (raw)

On Tue, Oct 25, 2011 at 11:36 AM, Stephen Rothwell <> wrote:
> Hi all,
> *Note well*
> This tree has nate had any build testing at all.  As such, it probably
> doesn't build :-) This tree is really just a roll up of the current state
> of the trees when the v3.2 merge window opened.  It will not be put into
> the build system referred to below.

I have generated a single linux-next (next-20111025) patch on top of
v3.1, it's approx. 100M!

$ du -h patch-v3.1-next-20111025.patch
96M     patch-v3.1-next-20111025.patch

I noticed this build-failure:

  CC      block/blk-throttle.o
  CC [M]  fs/fuse/dir.o
In function 'blk_throtl_drain':
error: implicit declaration of function 'lockdep_is_held'
cc1: some warnings being treated as errors

make[5]: *** [block/blk-throttle.o] Error 1
make[4]: *** [block] Error 2

This happens with Debian's gcc-4.6 (4.6.1-16) and default

- Sedat -

             reply	other threads:[~2011-10-25 13:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-25 13:04 Sedat Dilek [this message]
2011-10-25 13:10 ` linux-next: Tree for Oct 25 (block ?) Sedat Dilek
2011-10-25 13:38   ` Jens Axboe
2011-10-25 13:43     ` Sedat Dilek
2011-10-25 13:50       ` Jens Axboe
2011-10-25 13:55       ` Jens Axboe
2011-10-25 14:03         ` Sedat Dilek
2011-10-25 14:05           ` Jens Axboe

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \

* 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).