Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Sender: Larry Finger <larry.finger@gmail.com>
Message-ID: <bc873bd8-7163-65ca-6979-2b2c40edfe1a@lwfinger.net>
Date:   Sun, 20 Nov 2022 15:46:07 -0600
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.4.2
Subject: Re: Missing commit - Sent again with Kalle's correct address
Content-Language: en-US
To:     Kalle Valo <kvalo@kernel.org>
Cc:     Pkshih <pkshih@realtek.com>,
        linux-wireless <linux-wireless@vger.kernel.org>
References: <bea5e5c1-77e0-f210-e8bf-922492e50213@lwfinger.net>
 <87pmdhpbyv.fsf@kernel.org>
From:   Larry Finger <Larry.Finger@lwfinger.net>
In-Reply-To: <87pmdhpbyv.fsf@kernel.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 11/20/22 15:12, Kalle Valo wrote:
> That commit is in wireless-next and the first release having it should
> be v6.2-rc1, if all goes well. So the patch is not lost.
> 
> We need to get -next patches ready before the merge window opens, so it
> takes quite some time before patches go to an actual release. For
> example, the estimation for the v6.2 merge window to start is on
> 2022-12-11. This means that wireless patches should be submitted by
> latest 2022-12-05 to make the deadline, and even that's risky. The
> estimation for the final v6.2 release is 2023-02-19:

Kalle,

Thanks for the explanation. Things always take longer than expected.

Larry