From: Guenter Roeck <linux@roeck-us.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@lst.de>,
Trond Myklebust <trond.myklebust@primarydata.com>
Subject: Re: linux-next: Tree for Sep 19
Date: Fri, 19 Sep 2014 13:24:10 -0700 [thread overview]
Message-ID: <20140919202410.GA26329@roeck-us.net> (raw)
In-Reply-To: <20140919165817.225eb8b8@canb.auug.org.au>
On Fri, Sep 19, 2014 at 04:58:17PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20140917:
>
> The fsl tree still had its build failure so I used the version from
> next-20140917.
>
> The v4l-dvb tree lost its build failure.
>
> The security tree gained a conflict against the file-locks tree.
>
> Non-merge commits (relative to Linus' tree): 6014
> 5488 files changed, 217522 insertions(+), 129375 deletions(-)
>
> ----------------------------------------------------------------------------
>
i386:allyesconfig:
fs/built-in.o: In function `bl_map_stripe':
dev.c:(.text+0x3489ab): undefined reference to `__udivdi3'
dev.c:(.text+0x3489ca): undefined reference to `__umoddi3'
dev.c:(.text+0x348a83): undefined reference to `__udivdi3'
i386:allmodconfig:
mips:allmodconfig:
ERROR: "__udivdi3" [fs/nfs/blocklayout/blocklayoutdriver.ko] undefined!
ERROR: "__umoddi3" [fs/nfs/blocklayout/blocklayoutdriver.ko] undefined!
Obviously caused by commit 5c83746a0cf ('pnfs/blocklayout: in-kernel
GETDEVICEINFO XDR parsing') which adds fs/nfs/blocklayout/dev.c.
next prev parent reply other threads:[~2014-09-19 20:24 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 6:58 linux-next: Tree for Sep 19 Stephen Rothwell
2014-09-19 19:04 ` Guenter Roeck
2014-09-19 19:15 ` Guenter Roeck
2014-09-20 19:36 ` Helge Deller
2014-09-20 21:01 ` Guenter Roeck
2014-09-21 19:43 ` Helge Deller
2014-09-19 19:42 ` Guenter Roeck
2014-09-19 20:06 ` Guenter Roeck
2014-09-22 14:40 ` Christoph Hellwig
2014-09-19 20:24 ` Guenter Roeck [this message]
2014-09-22 14:35 ` Christoph Hellwig
2014-09-19 21:14 ` Guenter Roeck
2014-09-19 21:42 ` Anish Bhatt
2014-09-20 0:18 ` Guenter Roeck
2014-09-19 22:21 ` Randy Dunlap
2014-09-19 22:28 ` Anish Bhatt
2014-09-19 22:35 ` Randy Dunlap
2014-09-20 0:15 ` Guenter Roeck
2014-09-20 1:09 ` Randy Dunlap
2014-09-20 1:43 ` Anish Bhatt
2014-09-20 2:08 ` David Miller
2014-09-20 2:40 ` Guenter Roeck
-- strict thread matches above, loose matches on Subject: below --
2025-09-19 15:05 Mark Brown
2024-09-19 5:46 Stephen Rothwell
2023-09-19 6:37 Stephen Rothwell
2022-09-19 9:47 Stephen Rothwell
2019-09-19 16:06 Mark Brown
2018-09-19 6:16 Stephen Rothwell
2017-09-19 4:15 Stephen Rothwell
2016-09-19 7:02 Stephen Rothwell
2013-09-19 3:59 Stephen Rothwell
2013-09-19 3:59 ` 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=20140919202410.GA26329@roeck-us.net \
--to=linux@roeck-us.net \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=trond.myklebust@primarydata.com \
/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.