From: Kalle Valo <kvalo@kernel.org>
To: netdev@vger.kernel.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: pull-request: wireless-next-2022-10-28
Date: Fri, 28 Oct 2022 17:15:04 +0300 [thread overview]
Message-ID: <8735b8vxuf.fsf@kernel.org> (raw)
In-Reply-To: <20221028132943.304ECC433B5@smtp.kernel.org> (Kalle Valo's message of "Fri, 28 Oct 2022 13:29:43 +0000 (UTC)")
Kalle Valo <kvalo@kernel.org> writes:
> Note: wireless tree was merged[1] to wireless-next to avoid some
> conflicts with mac80211 patches between the trees. Unfortunately there
> are still two smaller conflicts in net/mac80211/util.c which Stephen
> also reported[2]. In the first conflict initialise scratch_len to
> "params->scratch_len ?: 3 * params->len" (note number 3, not 2!) and
> in the second conflict take the version which uses elems->scratch_pos.
>
> Git diff output should like this:
>
> --- a/net/mac80211/util.c
> +++ b/net/mac80211/util.c
> @@@ -1506,7 -1648,7 +1650,7 @@@ ieee802_11_parse_elems_full(struct ieee
> const struct element *non_inherit = NULL;
> u8 *nontransmitted_profile;
> int nontransmitted_profile_len = 0;
> - size_t scratch_len = params->len;
> - size_t scratch_len = params->scratch_len ?: 2 * params->len;
> ++ size_t scratch_len = params->scratch_len ?: 3 * params->len;
>
> elems = kzalloc(sizeof(*elems) + scratch_len, GFP_ATOMIC);
> if (!elems)
And in case want to see the final result, here's an example merge I
pushed to our pending branch:
https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git/tree/net/mac80211/util.c?h=pending&id=0879f594289e36546974c17f10bf587d9303e724#n1646
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-10-28 14:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 13:29 pull-request: wireless-next-2022-10-28 Kalle Valo
2022-10-28 14:15 ` Kalle Valo [this message]
2022-10-29 1:34 ` Jakub Kicinski
2022-10-29 20:54 ` Johannes Berg
2022-10-29 2:00 ` patchwork-bot+netdevbpf
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=8735b8vxuf.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).