From: "Jérôme Pouiller" <jerome.pouiller@silabs.com>
To: Kalle Valo <kvalo@kernel.org>
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>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v10 0/1] wfx: get out from the staging area
Date: Mon, 28 Feb 2022 17:00:56 +0100 [thread overview]
Message-ID: <2138665.7GXtrRnAus@pc-42> (raw)
In-Reply-To: <871qzpucyi.fsf@kernel.org>
+ Rob
+ devicetree
On Saturday 26 February 2022 11:41:41 CET Kalle Valo wrote:
> + 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?
Indeed, it seems Greg applied this patch[1] before Rob acked it.
However, the is DT now included in "make dt_binding_check" (because
it is now located in Documentation/devicetree/bindings/) and Rob
haven't raised any red flag.
[1]: https://lore.kernel.org/netdev/20220217103248.183770-1-Jerome.Pouiller@silabs.com/t/
> 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.
Right.
> 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.
--
Jérôme Pouiller
prev parent reply other threads:[~2022-02-28 16:01 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 ` [PATCH v10 0/1] " Kalle Valo
2022-02-26 12:56 ` 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 [this message]
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=2138665.7GXtrRnAus@pc-42 \
--to=jerome.pouiller@silabs.com \
--cc=davem@davemloft.net \
--cc=devel@driverdev.osuosl.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@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).