From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Miriam Rachel Korenblit <miriam.rachel.korenblit@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the iwlwifi-next tree with Linus' tree
Date: Wed, 7 May 2025 11:10:26 +1000 [thread overview]
Message-ID: <20250507111026.4700e392@canb.auug.org.au> (raw)
In-Reply-To: <f53576b21774ab6ba8294c5d1954f0528764f2fb.camel@sipsolutions.net>
[-- Attachment #1: Type: text/plain, Size: 2852 bytes --]
Hi Johannes,
On Tue, 06 May 2025 08:26:31 +0200 Johannes Berg <johannes@sipsolutions.net> wrote:
>
> > Today's linux-next merge of the iwlwifi-next tree got conflicts in:
> >
> > drivers/net/wireless/intel/iwlwifi/cfg/sc.c
> > drivers/net/wireless/intel/iwlwifi/iwl-config.h
> > drivers/net/wireless/intel/iwlwifi/iwl-nvm-parse.c
> > drivers/net/wireless/intel/iwlwifi/iwl-trans.c
> > drivers/net/wireless/intel/iwlwifi/iwl-trans.h
> > drivers/net/wireless/intel/iwlwifi/pcie/drv.c
> > drivers/net/wireless/intel/iwlwifi/tests/devinfo.c
> >
> > between various commits from Linus' tree and various commits from the
> > iwlwifi-next tree.
>
> Yeah, no surprise, there were some reverts in this area. The good thing
> is that we also already fixed the bugs that necessitated the reverts
> differently, so (eventually, need to check how much is in there now)
> this will just be "take next".
So, at your suggestion, I just used the latter versions of these files,
but I then got the following build failure:
In file included from arch/x86/include/asm/bug.h:103,
from include/linux/bug.h:5,
from include/linux/fortify-string.h:6,
from include/linux/string.h:392,
from include/linux/uuid.h:11,
from include/linux/mod_devicetable.h:14,
from include/linux/pci.h:27,
from drivers/net/wireless/intel/iwlwifi/pcie/trans.c:7:
drivers/net/wireless/intel/iwlwifi/pcie/trans.c: In function 'iwl_trans_pcie_reset':
drivers/net/wireless/intel/iwlwifi/pcie/trans.c:2337:29: error: 'IWL_RESET_MODE_BACKOFF' undeclared (first use in this function); did you mean 'IWL_RESET_MODE_REPROBE'?
2337 | mode == IWL_RESET_MODE_BACKOFF))
| ^~~~~~~~~~~~~~~~~~~~~~
include/asm-generic/bug.h:123:32: note: in definition of macro 'WARN_ON'
123 | int __ret_warn_on = !!(condition); \
| ^~~~~~~~~
drivers/net/wireless/intel/iwlwifi/pcie/trans.c:2337:29: note: each undeclared identifier is reported only once for each function it appears in
2337 | mode == IWL_RESET_MODE_BACKOFF))
| ^~~~~~~~~~~~~~~~~~~~~~
include/asm-generic/bug.h:123:32: note: in definition of macro 'WARN_ON'
123 | int __ret_warn_on = !!(condition); \
| ^~~~~~~~~
So, today I have merged the iwlwifi-next tree from next-20250505 (which
was effectively empty). You may want to try merging the iwlwifi tree
into the iwlwifi-next tree and resolve any conflicts yourself (now that
the iwlwifi tree has been merged into Linus' tree).
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-05-07 1:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 1:44 linux-next: manual merge of the iwlwifi-next tree with Linus' tree Stephen Rothwell
2025-05-06 6:26 ` Johannes Berg
2025-05-07 1:10 ` Stephen Rothwell [this message]
2025-05-07 5:37 ` Johannes Berg
2025-05-08 3:24 ` Stephen Rothwell
2025-05-14 2:41 ` Stephen Rothwell
2025-05-14 2:55 ` Stephen Rothwell
2025-05-14 6:41 ` Johannes Berg
2025-05-14 7:36 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2025-05-08 3:48 Stephen Rothwell
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=20250507111026.4700e392@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=miriam.rachel.korenblit@intel.com \
/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