From: Kalle Valo <kvalo@codeaurora•org>
To: Randy Dunlap <rdunlap@infradead•org>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Luca Coelho <luciano.coelho@intel•com>,
linux-wireless <linux-wireless@vger•kernel.org>
Subject: Re: linux-next: Tree for Feb 23 [drivers/net/wireless/intel/iwlwifi/iwlwifi.ko]
Date: Thu, 25 Feb 2021 10:13:50 +0200 [thread overview]
Message-ID: <87r1l4ef9d.fsf@tynnyri.adurom.net> (raw)
In-Reply-To: <a3f440a5-2178-ffd8-a043-25b18fa42f0f@infradead.org> (Randy Dunlap's message of "Tue, 23 Feb 2021 11:52:13 -0800")
Randy Dunlap <rdunlap@infradead•org> writes:
> On 2/22/21 10:35 PM, Stephen Rothwell wrote:
>> Hi all,
>>
>> Please do not add any changes destined for v5.13 to your linux-next
>> included branches until after v5.12-rc1 has been released.
>>
>> Changes since 20210222:
>>
>
> Still seeing this build error on x86_64:
>
> ERROR: modpost: "iwl_so_trans_cfg" [drivers/net/wireless/intel/iwlwifi/iwlwifi.ko] undefined!
>
>
> Full randconfig file is attached.
Still? I don't recall seeing this report before, but maybe I have missed
it. Anyway, I sent a fix but it would be great if you can test it:
https://patchwork.kernel.org/project/linux-wireless/patch/1614236661-20274-1-git-send-email-kvalo@codeaurora.org/
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2021-02-25 8:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 6:35 linux-next: Tree for Feb 23 Stephen Rothwell
2021-02-23 19:52 ` linux-next: Tree for Feb 23 [drivers/net/wireless/intel/iwlwifi/iwlwifi.ko] Randy Dunlap
2021-02-25 8:13 ` Kalle Valo [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=87r1l4ef9d.fsf@tynnyri.adurom.net \
--to=kvalo@codeaurora$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-wireless@vger$(echo .)kernel.org \
--cc=luciano.coelho@intel$(echo .)com \
--cc=rdunlap@infradead$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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