From: Kalle Valo <kvalo@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Jakub Kicinski <kuba@kernel.org>,
devel@driverdev.osuosl.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
"David S . Miller" <davem@davemloft.net>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH v10 0/1] wfx: get out from the staging area
Date: Tue, 12 Apr 2022 17:42:29 +0300 [thread overview]
Message-ID: <871qy2nz1m.fsf@kernel.org> (raw)
In-Reply-To: <Yk8iiZKFpYNgCbCz@kroah.com> (Greg Kroah-Hartman's message of "Thu, 7 Apr 2022 19:42:33 +0200")
+ stephen
Greg Kroah-Hartman <gregkh@linuxfoundation.org> writes:
> On Wed, Apr 06, 2022 at 10:06:33AM +0300, Kalle Valo wrote:
>> Jakub Kicinski <kuba@kernel.org> writes:
>>
>> > On Tue, 05 Apr 2022 10:16:58 +0300 Kalle Valo wrote:
>> >> Sure, that would technically work. But I just think it's cleaner to use
>> >> -rc1 (or later) as the baseline for an immutable branch. If the baseline
>> >> is an arbitrary commit somewhere within merge windows commits, it's more
>> >> work for everyone to verify the branch is suitable.
>> >>
>> >> Also in general I would also prefer to base -next trees to -rc1 or newer
>> >> to make the bisect cleaner. The less we need to test kernels from the
>> >> merge window (ie. commits after the final release and before -rc1) the
>> >> better.
>> >>
>> >> But this is just a small wish from me, I fully understand that it might
>> >> be too much changes to your process. Wanted to point out this anyway.
>> >
>> > Forwarded!
>>
>> Awesome, thank you Jakub!
>>
>> Greg, I now created an immutable branch for moving wfx from
>> drivers/staging to drivers/net/wireless/silabs:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git
>> wfx-move-out-of-staging
>>
>> The baseline for this branch is v5.18-rc1. If you think the branch is
>> ok, please pull it to staging-next and let me know. I can then pull the
>> branch to wireless-next and the transition should be complete. And do
>> let me know if there are any problems.
>
> Looks great to me! I've pulled it into staging-next now. And will not
> take any more patches to the driver (some happened before the merge but
> git handled the move just fine.)
Great, thanks Greg! I now merged the immutable branch also to
wireless-next:
79649041edc8 Merge branch 'wfx-move-out-of-staging'
4a5fb1bbcdf1 wfx: get out from the staging area
So from now on wfx patches should be submitted for wireless-next via the
linux-wireless mailing list, instructions in the wiki link below.
Stephen, I want to warn you in advance about this driver move but
hopefully everything goes smoothly.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-04-12 14:42 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 [this message]
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=871qy2nz1m.fsf@kernel.org \
--to=kvalo@kernel.org \
--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 \
--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 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.