From: Jan Kara <jack@suse.cz>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jan Kara <jack@suse.cz>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the ext3 tree
Date: Thu, 31 Jan 2019 11:11:22 +0100 [thread overview]
Message-ID: <20190131101122.GD19222@quack2.suse.cz> (raw)
In-Reply-To: <20190131151411.7e8b89b3@canb.auug.org.au>
On Thu 31-01-19 15:14:11, Stephen Rothwell wrote:
> Hi Jan,
>
> After merging the ext3 tree, today's linux-next build (powerpc
> ppc44x_defconfig) failed like this:
>
> ld: fs/ext2/super.o: in function `ext2_fill_super':
> super.c:(.text+0x1494): undefined reference to `__divdi3'
> ld: super.c:(.text+0x14bc): undefined reference to `__divdi3'
>
> Caused by commit
>
> 455d38a0e62f ("ext2: Fix underflow in ext2_max_size()")
>
> I have reverted that commit for today.
Yeah, I've fixed that already in my tree. Thanks for letting me know and
sorry for the breakage.
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2019-01-31 10:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 4:14 linux-next: build failure after merge of the ext3 tree Stephen Rothwell
2019-01-31 10:11 ` Jan Kara [this message]
2019-01-31 22:09 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2024-03-07 0:07 Stephen Rothwell
2024-03-07 6:18 ` Winston Wen
2024-03-07 12:03 ` Jan Kara
2023-08-16 0:37 Stephen Rothwell
2020-11-12 23:47 Stephen Rothwell
2020-11-13 10:33 ` Jan Kara
2014-08-08 1:52 Stephen Rothwell
2014-08-08 9:22 ` Jan Kara
2011-12-28 0:22 Stephen Rothwell
2012-01-02 22:40 ` Jan Kara
2010-03-02 0:36 Stephen Rothwell
2010-03-02 9:07 ` Christoph Hellwig
2010-03-02 17:27 ` Jan Kara
2010-03-03 0:42 ` 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=20190131101122.GD19222@quack2.suse.cz \
--to=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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;
as well as URLs for NNTP newsgroup(s).