From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Kalle Valo <kvalo@kernel.org>,
Johannes Berg <johannes@sipsolutions.net>,
Al Viro <viro@zeniv.linux.org.uk>,
Johannes Berg <johannes.berg@intel.com>,
Wireless <linux-wireless@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Tree Davies <tdavies@darkphysics.net>
Subject: Re: linux-next: manual merge of the wireless-next tree with Linus' tree
Date: Wed, 9 Oct 2024 08:43:36 +0200 [thread overview]
Message-ID: <2024100945-engross-appraisal-d1f0@gregkh> (raw)
In-Reply-To: <20241009114455.52db31ad@canb.auug.org.au>
On Wed, Oct 09, 2024 at 11:44:55AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the wireless-next tree got conflicts in:
>
> drivers/staging/rtl8192e/rtl8192e/r8190P_def.h
> drivers/staging/rtl8192e/rtl8192e/r8192E_cmdpkt.c
> drivers/staging/rtl8192e/rtl8192e/r8192E_dev.c
> drivers/staging/rtl8192e/rtl8192e/r8192E_hw.h
> drivers/staging/rtl8192e/rtl8192e/r8192E_phy.c
> drivers/staging/rtl8192e/rtl8192e/r8192E_phy.h
> drivers/staging/rtl8192e/rtl8192e/rtl_core.c
> drivers/staging/rtl8192e/rtl8192e/rtl_core.h
> drivers/staging/rtl8192e/rtl8192e/rtl_dm.c
> drivers/staging/rtl8192e/rtl8192e/rtl_ps.c
> drivers/staging/rtl8192e/rtl8192e/rtl_wx.c
> drivers/staging/rtl8192e/rtl819x_BAProc.c
> drivers/staging/rtl8192e/rtl819x_HTProc.c
> drivers/staging/rtl8192e/rtl819x_TSProc.c
> drivers/staging/rtl8192e/rtllib.h
> drivers/staging/rtl8192e/rtllib_rx.c
> drivers/staging/rtl8192e/rtllib_softmac_wx.c
>
> between commits:
>
> 5f60d5f6bbc1 ("move asm/unaligned.h to linux/unaligned.h")
> 5e6bf74d63c2 ("Staging: rtl8192e: Rename variable RxDrvInfoSize")
> and many others
>
> from Linus' tree (pre v6.12-rc2) and commit:
>
> be9be9f54f22 ("staging: rtl8192e: delete the driver")
>
> from the wireless-next tree.
>
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging. You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.
Johannes, any objection if I just pull in your wireless-next tree into
my staging-next branch so that we don't get these issues going forward?
It's not going to be rebased, right?
thanks,
greg k-h
next prev parent reply other threads:[~2024-10-09 6:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 0:44 linux-next: manual merge of the wireless-next tree with Linus' tree Stephen Rothwell
2024-10-09 6:43 ` Greg Kroah-Hartman [this message]
2024-10-09 6:51 ` Johannes Berg
2024-10-09 7:13 ` Greg Kroah-Hartman
2024-10-09 7:19 ` Johannes Berg
2024-10-09 7:27 ` Greg Kroah-Hartman
2024-10-09 8:30 ` Johannes Berg
2024-10-09 9:24 ` Greg Kroah-Hartman
-- strict thread matches above, loose matches on Subject: below --
2024-10-09 0:38 Stephen Rothwell
2023-09-26 1:54 Stephen Rothwell
2023-09-26 4:50 ` Greg Kroah-Hartman
2023-09-14 0:28 Stephen Rothwell
2022-10-19 16:23 Stephen Rothwell
2022-10-19 23:23 ` Jakub Kicinski
2022-10-19 17:14 ` Stephen Rothwell
2022-10-19 23:52 ` Jakub Kicinski
2022-10-26 12:40 ` Kalle Valo
2022-10-26 14:35 ` Kalle Valo
2022-10-26 14:50 ` Kalle Valo
2013-07-25 1:37 Stephen Rothwell
2013-01-23 1:16 Stephen Rothwell
2013-01-23 20:18 ` Grumbach, Emmanuel
2011-11-22 3:20 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=2024100945-engross-appraisal-d1f0@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tdavies@darkphysics.net \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.