From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Chris Mason <chris.mason@fusionio.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Stefan Behrens <sbehrens@giantdisaster.de>,
Josef Bacik <jbacik@fusionio.com>,
Linus <torvalds@linux-foundation.org>
Subject: linux-next: build failure after merge of the btrfs tree
Date: Mon, 17 Dec 2012 10:00:22 +1100 [thread overview]
Message-ID: <20121217100022.7d751dc9075d60a33d636a23@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 901 bytes --]
Hi Chris,
After merging the btrfs tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
fs/btrfs/ioctl.c: In function 'btrfs_ioctl':
fs/btrfs/ioctl.c:3940:7: error: case label does not reduce to an integer constant
Caused by commit 0aa7cbc7585a ("Btrfs: add support for device replace ioctls").
I have used the btrfs tree from next-20121214 for today (which was empty).
I have to say that these btrfs commits have come to linux-next very late
in the game (i.e. some of them have author dates back in September and
October and yet they only appeared in linux-next today). Also, the
committer of this commits is Josef Bacik <jbacik@fusionio.com> but there
is not Signed-off-by him. There are other commits that are committed by
you, Chris, that also do not have a Signed-off-by you.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2012-12-16 23:00 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-16 23:00 Stephen Rothwell [this message]
2012-12-17 0:15 ` linux-next: build failure after merge of the btrfs tree Chris Mason
2012-12-17 2:52 ` Chris Mason
2012-12-17 3:13 ` Stephen Rothwell
2012-12-17 3:38 ` Chris Mason
2012-12-17 2:01 ` Chris Mason
-- strict thread matches above, loose matches on Subject: below --
2023-01-12 23:36 Stephen Rothwell
2023-01-13 10:59 ` David Sterba
2022-11-07 22:42 Stephen Rothwell
2022-11-08 11:21 ` David Sterba
2022-09-06 19:44 Stephen Rothwell
2022-08-21 23:44 Stephen Rothwell
2021-10-27 10:09 Stephen Rothwell
2021-10-29 8:28 ` Stephen Rothwell
2021-10-29 9:52 ` David Sterba
2021-10-29 10:50 ` David Sterba
[not found] ` <CAHp75VdXJEuY86pFC+bLoGbAYuGsA+KqEV-g4Dca25HHD-njHA@mail.gmail.com>
2021-10-29 12:14 ` David Sterba
2021-10-31 4:30 ` Stephen Rothwell
2021-10-08 4:03 Stephen Rothwell
2021-10-08 5:56 ` Qu Wenruo
2020-04-21 0:25 Stephen Rothwell
2020-04-21 0:40 ` Qu Wenruo
2020-04-21 1:13 ` Stephen Rothwell
2020-04-21 1:33 ` Qu Wenruo
2020-04-21 1:55 ` Stephen Rothwell
2020-04-22 21:29 ` David Sterba
2020-04-24 5:17 ` Qu Wenruo
2020-02-19 22:23 Stephen Rothwell
2020-02-21 11:30 ` David Sterba
2020-02-21 11:33 ` David Sterba
2015-08-21 0:42 Stephen Rothwell
2012-10-01 4:22 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=20121217100022.7d751dc9075d60a33d636a23@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=chris.mason@fusionio.com \
--cc=jbacik@fusionio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sbehrens@giantdisaster.de \
--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.