From: Kalle Valo <kvalo@kernel.org>
To: Jerome Pouiller <Jerome.Pouiller@silabs.com>
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>
Subject: Re: [PATCH v10 0/1] wfx: get out from the staging area
Date: Sat, 26 Feb 2022 12:41:41 +0200 [thread overview]
Message-ID: <871qzpucyi.fsf@kernel.org> (raw)
In-Reply-To: <20220226092142.10164-1-Jerome.Pouiller@silabs.com> (Jerome Pouiller's message of "Sat, 26 Feb 2022 10:21:41 +0100")
+ jakub
Jerome Pouiller <Jerome.Pouiller@silabs.com> writes:
> The firmware and the PDS files (= antenna configurations) are now a part of
> the linux-firmware repository.
>
> All the issues have been fixed in staging tree. I think we are ready to get
> out from the staging tree for the kernel 5.18.
[...]
> rename Documentation/devicetree/bindings/{staging => }/net/wireless/silabs,wfx.yaml (98%)
I lost track, is this file acked by the DT maintainers now?
What I suggest is that we queue this for v5.19. After v5.18-rc1 is
released I could create an immutable branch containing this one commit.
Then I would merge the branch to wireless-next and Greg could merge it
to the staging tree, that way we would minimise the chance of conflicts
between trees.
Greg, what do you think? Would this work for you? IIRC we did the same
with wilc1000 back in 2020 and I recall it went without hiccups.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-02-26 10:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-26 9:21 [PATCH v10 0/1] wfx: get out from the staging area Jerome Pouiller
2022-02-26 9:21 ` [PATCH v10 1/1] " Jerome Pouiller
2022-02-26 10:41 ` Kalle Valo [this message]
2022-02-26 12:56 ` [PATCH v10 0/1] " Greg Kroah-Hartman
2022-02-26 13:15 ` Kalle Valo
2022-04-04 9:31 ` Jérôme Pouiller
2022-04-04 10:49 ` Kalle Valo
2022-04-05 6:22 ` Jakub Kicinski
2022-04-05 6:29 ` Jakub Kicinski
2022-04-05 7:16 ` Kalle Valo
2022-04-05 16:20 ` Jakub Kicinski
2022-04-06 7:06 ` Kalle Valo
2022-04-07 17:42 ` Greg Kroah-Hartman
2022-04-12 14:42 ` Kalle Valo
2022-02-28 16:00 ` Jérôme Pouiller
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=871qzpucyi.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=Jerome.Pouiller@silabs.com \
--cc=davem@davemloft.net \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.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).