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>,
Wireless <linux-wireless@vger.kernel.org>,
Aloka Dixit <quic_alokad@quicinc.com>,
Franziska Naepelt <franziska.naepelt@googlemail.com>,
Johannes Berg <johannes.berg@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 wireless-next tree with Linus' tree
Date: Tue, 26 Sep 2023 06:50:57 +0200 [thread overview]
Message-ID: <2023092650-nastily-cube-30de@gregkh> (raw)
In-Reply-To: <20230926115452.68a71261@canb.auug.org.au>
On Tue, Sep 26, 2023 at 11:54:52AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the wireless-next tree got a conflict in:
>
> drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c
>
> between commit:
>
> 1d85bb7fd66a ("staging: rtl8723bs: Fix alignment open parenthesis")
>
> from Linus' tree and commit:
>
> 66f85d57b710 ("wifi: cfg80211: modify prototype for change_beacon")
> bb55441c57cc ("wifi: cfg80211: split struct cfg80211_ap_settings")
>
> 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.
>
> --
> Cheers,
> Stephen Rothwell
>
> diff --cc drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c
> index af155fca39b8,1e683212027c..000000000000
> --- a/drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c
> +++ b/drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c
> @@@ -2317,9 -2318,8 +2317,9 @@@ static int cfg80211_rtw_start_ap(struc
> return ret;
> }
>
> -static int cfg80211_rtw_change_beacon(struct wiphy *wiphy, struct net_device *ndev,
> - struct cfg80211_ap_update *info)
> +static int cfg80211_rtw_change_beacon(struct wiphy *wiphy,
> + struct net_device *ndev,
> - struct cfg80211_beacon_data *info)
> ++ struct cfg80211_ap_update *info)
> {
> struct adapter *adapter = rtw_netdev_priv(ndev);
>
Looks good to me, thanks!
greg k-h
next prev parent reply other threads:[~2023-09-26 4:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 1:54 linux-next: manual merge of the wireless-next tree with Linus' tree Stephen Rothwell
2023-09-26 4:50 ` Greg Kroah-Hartman [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-09 0:44 Stephen Rothwell
2024-10-09 6:43 ` Greg Kroah-Hartman
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
2024-10-09 0:38 Stephen Rothwell
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
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=2023092650-nastily-cube-30de@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=franziska.naepelt@googlemail.com \
--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=quic_alokad@quicinc.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;
as well as URLs for NNTP newsgroup(s).