From: Johannes Berg <johannes@sipsolutions.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
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, 07 May 2025 07:37:46 +0200 [thread overview]
Message-ID: <3d5761da40d0ddf4109d10d6f3c3d2538c4d89d4.camel@sipsolutions.net> (raw)
In-Reply-To: <20250507111026.4700e392@canb.auug.org.au>
Hi Stephen,
Thanks!
> So, at your suggestion, I just used the latter versions of these files,
> but I then got the following build failure:
Ouch, sorry about that. That sounds like it's due to the duplicate
commits you had pointed out, which Miri dropped from iwlwifi-next now.
On the plus side, I'm going to be the one who has to resolve these
conflicts (soon) :)
> 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).
Not sure what you mean by "iwlwifi tree", I think iwlwifi-next/fixes was
empty, so perhaps you meant "wireless tree" instead?
But yeah, I know what all the code is and what's going on, though
evidently less than I thought after the recent updates.
johannes
next prev parent reply other threads:[~2025-05-07 5:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 1:44 Stephen Rothwell
2025-05-06 6:26 ` Johannes Berg
2025-05-07 1:10 ` Stephen Rothwell
2025-05-07 5:37 ` Johannes Berg [this message]
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
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=3d5761da40d0ddf4109d10d6f3c3d2538c4d89d4.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=miriam.rachel.korenblit@intel.com \
--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
all inboxes | Powered by JetHome®