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>,
linux-wireless <linux-wireless@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: linux-next: Tree for Feb 11 (wireless/80211)
Date: Mon, 11 Feb 2019 09:07:05 -0800 [thread overview]
Message-ID: <80b32344-08c9-0d8b-fdae-1db9b1003f60@infradead.org> (raw)
In-Reply-To: <20190211183951.3fe1dad9@canb.auug.org.au>
On 2/10/19 11:39 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20190208:
>
on i386:
ERROR: "__umoddi3" [net/wireless/cfg80211.ko] undefined!
ERROR: "__umoddi3" [net/mac80211/mac80211.ko] undefined!
--
~Randy
next prev parent reply other threads:[~2019-02-11 17:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 7:39 linux-next: Tree for Feb 11 Stephen Rothwell
2019-02-11 17:07 ` Randy Dunlap [this message]
2019-02-13 8:04 ` linux-next: Tree for Feb 11 (wireless/80211) Johannes Berg
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=80b32344-08c9-0d8b-fdae-1db9b1003f60@infradead.org \
--to=rdunlap@infradead.org \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--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 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).