From: Ingo Molnar <mingo@kernel.org>
To: Chris Mason <chris.mason@oracle.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [build breakage] Re: [GIT PULL] Btrfs pull round two
Date: Fri, 19 Aug 2011 15:06:15 +0200 [thread overview]
Message-ID: <20110819130615.GA6307@kernel.org> (raw)
In-Reply-To: <1312315404-sup-6084@shiny>
* Chris Mason <chris.mason@oracle.com> wrote:
> Hi everyone,
>
> This has the rest of the btrfs cleanups for 3.1. The bulk of this is
> error handing fixes from SUSE and cleanups from Fujitsu.
I havent seen a lkml mail of this pull request:
5c80c71b9a0e: Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-unstable
so i'm following up on this earlier pull request.
the aptly named btrfs-unstable branch indeed does not even build on
x86 defconfig (32-bit):
LD .tmp_vmlinux1
fs/built-in.o: In function `btrfs_can_relocate':
(.text+0x1d6605): undefined reference to `__udivdi3'
make: *** [.tmp_vmlinux1] Error 1
and given that most of the commits:
81d86e1b7096: Merge branch 'btrfs-3.0' into for-linus
f1e490a7ebe4: Btrfs: set i_size properly when fallocating and we already
9a4327ca1f45: btrfs: unlock on error in btrfs_file_llseek()
cb6db4e57632: btrfs: btrfs_permission's RO check shouldn't apply to device nodes
f81c9cdc567c: Btrfs: truncate pages from clone ioctl target range
0e588859618b: Btrfs: fix uninitialized sync_pending
bb3ac5a4dfc8: Btrfs: fix wrong free space information
f4ac904c411b: btrfs: memory leak in btrfs_add_inode_defrag()
c97c2916e25c: Btrfs: use plain page_address() in header fields setget functions
cb1b69f4508a: Btrfs: forced readonly when btrfs_drop_snapshot() fails
cdcb725c05fe: Btrfs: check if there is enough space for balancing smarter
38c01b960592: Btrfs: fix a bug of balance on full multi-disk partitions
34f3e4f23ca3: Btrfs: fix an oops of log replay
d5e2003c2bcd: Btrfs: detect wether a device supports discard
93ee7a9340d6: Linux 3.1-rc2
were committed after -rc2 and were at most a couple of hours old
before you sent them off to Linus, did you really expect any other
outcome than breaking upstream in trivial ways? :-)
Thanks,
Ingo
next prev parent reply other threads:[~2011-08-19 13:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-02 20:33 [GIT PULL] Btrfs pull round two Chris Mason
2011-08-19 13:06 ` Ingo Molnar [this message]
2011-08-19 13:18 ` [build breakage] " Ingo Molnar
2011-08-19 13:24 ` Josh Boyer
2011-08-19 13:24 ` Josh Boyer
2011-08-19 15:14 ` Linus Torvalds
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=20110819130615.GA6307@kernel.org \
--to=mingo@kernel.org \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.