From: Alex Elder <elder@ieee.org>
To: Randy Dunlap <rdunlap@infradead.org>,
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>,
Alex Elder <elder@kernel.org>
Subject: Re: linux-next: Tree for Mar 22 (net/ipa)
Date: Mon, 22 Mar 2021 12:41:37 -0500 [thread overview]
Message-ID: <33380a70-c594-cefe-14b8-c1fbf2dd90af@ieee.org> (raw)
In-Reply-To: <83366bbc-af28-4ffd-2a25-f688a52f9239@infradead.org>
On 3/22/21 12:16 PM, Randy Dunlap wrote:
> On 3/22/21 12:52 AM, Stephen Rothwell wrote:
>> Hi all,
>>
>> Warning: Some of the branches in linux-next may still based on v5.12-rc1,
>> so please be careful if you are trying to bisect a bug.
>>
>> News: if your -next included tree is based on Linus' tree tag
>> v5.12-rc1{,-dontuse} (or somewhere between v5.11 and that tag), please
>> consider rebasing it onto v5.12-rc2. Also, please check any branches
>> merged into your branch.
>>
>> Changes since 20210319:
>>
>
>
> on i386:
>
> ld: drivers/net/ipa/gsi.o: in function `gsi_ring_alloc':
> gsi.c:(.text+0x926): undefined reference to `__umoddi3'
This code assumes a 32-bit kernel implies a 32-bit dma_addr_t.
But it seems that's not the case for i386...
Let me try to reproduce this. The fix should be easy.
Sorry about that.
-Alex
prev parent reply other threads:[~2021-03-22 17:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 7:52 linux-next: Tree for Mar 22 Stephen Rothwell
2021-03-22 17:16 ` linux-next: Tree for Mar 22 (net/ipa) Randy Dunlap
2021-03-22 17:41 ` Alex Elder [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=33380a70-c594-cefe-14b8-c1fbf2dd90af@ieee.org \
--to=elder@ieee.org \
--cc=elder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@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 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).