From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Chao Yu <yuchao0@huawei.com>,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: linux-next: Tree for Nov 23 (f2fs)
Date: Wed, 23 Nov 2016 10:11:22 -0800 [thread overview]
Message-ID: <20161123181122.GA24137@jaegeuk> (raw)
In-Reply-To: <320e8cf0-a0ee-8178-9aec-b8c0002ceb6d@infradead.org>
Hello,
On Wed, Nov 23, 2016 at 08:00:57AM -0800, Randy Dunlap wrote:
> On 11/22/16 22:58, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20161122:
> >
>
> on i386:
>
> fs/built-in.o: In function `__issue_discard_async':
> segment.c:(.text+0x5e2135): undefined reference to `__umoddi3'
>
> or when built as a loadable module:
> ERROR: "__umoddi3" [fs/f2fs/f2fs.ko] undefined!
It seems Arnd's patch deals with this.
I'll keep an eye on this.
Thanks,
>
>
> --
> ~Randy
prev parent reply other threads:[~2016-11-23 18:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20161123175848.5b56c35c@canb.auug.org.au>
2016-11-23 16:00 ` linux-next: Tree for Nov 23 (f2fs) Randy Dunlap
2016-11-23 18:11 ` Jaegeuk Kim [this message]
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=20161123181122.GA24137@jaegeuk \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=yuchao0@huawei.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 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).