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, 14 May 2025 08:41:35 +0200 [thread overview]
Message-ID: <958ec4672d9263d23b1f47d8acd1047037e7ff25.camel@sipsolutions.net> (raw)
In-Reply-To: <20250514125524.1528467f@canb.auug.org.au>
Hi Stephen,
> > I keep getting more conflicts in the above files (each time one of them
> > get modified in the iwlwifi-next tree. Could you please merge commit
> >
> > ebedf8b7f05b ("wifi: iwlwifi: add support for Killer on MTL")
> >
> > or the current net tree
> > (git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git#main)
> > into the iwlwifi-next tree and fix up the conflicts. I believe that
> > will clean up all the conflicts - that are really just between bug
> > fixes for iwlwifi and the new development).
>
> Or, of course, I assume the iwlwifi-next tree will be merged into the
> net-next tree at some point soon ...
>
Yes, should be really soon now, though into wireless-next. But that's
up-to-date with net, so would resolve all of these issues. In fact that
was the plan all along, it's just been taking a bit longer than
expected, sorry about that.
johannes
next prev parent reply other threads:[~2025-05-14 6:41 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
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 [this message]
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=958ec4672d9263d23b1f47d8acd1047037e7ff25.camel@sipsolutions.net \
--to=johannes@sipsolutions$(echo .)net \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=miriam.rachel.korenblit@intel$(echo .)com \
--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