From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux-Next Mailing List <linux-next@vger.kernel.org>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Björn Töpel" <bjorn.topel@intel.com>,
"Magnus Karlsson" <magnus.karlsson@intel.com>
Subject: Re: linux-next: Tree for May 7 (net/xdp)
Date: Mon, 7 May 2018 09:17:42 -0700 [thread overview]
Message-ID: <e9890e95-16b4-4540-301b-43f17a824808@infradead.org> (raw)
In-Reply-To: <20180507153147.166ee38a@canb.auug.org.au>
On 05/06/2018 10:31 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20180504:
>
on i386:
net/xdp/xdp_umem.o: In function `xdp_umem_reg':
xdp_umem.c:(.text+0x47e): undefined reference to `__udivdi3'
--
~Randy
next prev parent reply other threads:[~2018-05-07 16:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 5:31 linux-next: Tree for May 7 Stephen Rothwell
2018-05-07 12:13 ` Geert Uytterhoeven
2018-05-07 12:25 ` Stephen Rothwell
2018-05-07 16:17 ` Randy Dunlap [this message]
2018-05-07 17:43 ` [PATCH bpf-next] xsk: fix 64-bit division Björn Töpel
2018-05-07 18:25 ` Randy Dunlap
2018-05-09 16:13 ` Daniel Borkmann
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=e9890e95-16b4-4540-301b-43f17a824808@infradead.org \
--to=rdunlap@infradead.org \
--cc=bjorn.topel@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=magnus.karlsson@intel.com \
--cc=netdev@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 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.