From: Mike Snitzer <snitzer@redhat.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Joe Thornber <dm-devel@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Sep 13 (dm-thin-pool)
Date: Thu, 13 Sep 2018 14:51:48 -0400 [thread overview]
Message-ID: <20180913185147.GA5647@redhat.com> (raw)
In-Reply-To: <258e14a1-0dbc-74ff-23a5-cd676fdf4579@infradead.org>
On Thu, Sep 13 2018 at 1:28pm -0400,
Randy Dunlap <rdunlap@infradead.org> wrote:
> On 9/12/18 10:27 PM, Stephen Rothwell wrote:
> > Hi all,
> >
> > News: there will be no linux-next releases on Friday or Monday.
> >
> > Changes since 20180912:
> >
>
> on i386:
>
> ERROR: "__udivdi3" [drivers/md/dm-thin-pool.ko] undefined!
Well, as I pointed out in reply that nobody will see to the buildbots:
There is something off in this report... I cannot reproduce. It is
almost like the warning was generated when building an older version of
this change, but then reported against the latest commit.
I switched to sector_div() specifically because of the undefined
__udivdi3 error.
So I'm ignoring this given I cannot reproduce when using 'make ARCH=i386'
next prev parent reply other threads:[~2018-09-13 18:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 5:27 linux-next: Tree for Sep 13 Stephen Rothwell
2018-09-13 17:14 ` linux-next: Tree for Sep 13 (drivers/media/platform/imx-pxp) Randy Dunlap
2018-09-13 17:28 ` linux-next: Tree for Sep 13 (dm-thin-pool) Randy Dunlap
2018-09-13 18:51 ` Mike Snitzer [this message]
2018-09-14 0:45 ` Randy Dunlap
2018-09-14 1:14 ` Mike Snitzer
2018-09-14 1:14 ` Mike Snitzer
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=20180913185147.GA5647@redhat.com \
--to=snitzer@redhat.com \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.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 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.