Received-SPF: pass (google.com: domain of linux-wireless+bounces-2594-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
Message-ID: <ca28cb35-ebe9-4f20-8a71-a9fcef1decbc@quicinc.com>
Date: Sat, 27 Jan 2024 10:31:05 +0530
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PATCH v5 3/3] wifi: mac80211: update beacon counters per link
 basis
Content-Language: en-US
To: Johannes Berg <johannes@sipsolutions.net>
CC: <linux-wireless@vger.kernel.org>
References: <20240125130410.827701-1-quic_adisi@quicinc.com>
 <20240125130410.827701-4-quic_adisi@quicinc.com>
 <dca9bc4a793f338d4681f3a2a1f2e326f0b5d9ec.camel@sipsolutions.net>
From: Aditya Kumar Singh <quic_adisi@quicinc.com>
In-Reply-To: <dca9bc4a793f338d4681f3a2a1f2e326f0b5d9ec.camel@sipsolutions.net>
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: 7bit

On 1/26/24 15:01, Johannes Berg wrote:
> On Thu, 2024-01-25 at 18:34 +0530, Aditya Kumar Singh wrote:
>> Currently, function to update beacon counter uses deflink to fetch
>> the beacon and then update the counter. However, with MLO, there is
>> a need to update the counter for the beacon in a particular link.
>>
>> Add support to use link_id in order to fetch the beacon from a particular
>> link data during beacon update counter.
>>
> 
> Seems it would make sense to put this patch _before_ patch 2, since
> otherwise in patch 2 it would appear to be kind of working but then not
> really work?
> 

You are right! I will move this to before [2] then followed by 
csa_finish() changes and then last patch would be to start csa process 
on given link. Looks fine?