From: Aditya Kumar Singh <quic_adisi@quicinc.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v7 1/5] wifi: cfg80211: send link id in channel_switch ops
Date: Tue, 30 Jan 2024 16:05:39 +0530 [thread overview]
Message-ID: <c3ce6010-5cd2-4693-a43c-c89947cdb047@quicinc.com> (raw)
In-Reply-To: <184a2907d637cd924160681b40f1caffa2fa1e92.camel@sipsolutions.net>
On 1/30/24 15:43, Johannes Berg wrote:
> On Tue, 2024-01-30 at 10:02 +0530, Aditya Kumar Singh wrote:
>>
>> + * @link_id: defines the link on which channel switch is expected during
>> + * MLO. 0 in case of non-MLO.
>
> please still use a tab (only) :)
>
Now I get your point. I was using tab as much as possible and then
spaces to align it to ':'. You are suggesting to just use tabs alone right?
next prev parent reply other threads:[~2024-01-30 10:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 4:32 [PATCH v7 0/5] wifi: cfg80211/mac80211: add link_id handling in AP channel switch during Multi-Link Operation Aditya Kumar Singh
2024-01-30 4:32 ` [PATCH v7 1/5] wifi: cfg80211: send link id in channel_switch ops Aditya Kumar Singh
2024-01-30 10:13 ` Johannes Berg
2024-01-30 10:35 ` Aditya Kumar Singh [this message]
2024-01-30 10:36 ` Johannes Berg
2024-01-30 4:32 ` [PATCH v7 2/5] wifi: mac80211: update beacon counters per link basis Aditya Kumar Singh
2024-01-30 4:32 ` [PATCH v7 3/5] wifi: mac80211: handle set csa/after_csa beacon on " Aditya Kumar Singh
2024-01-30 10:17 ` Johannes Berg
2024-01-30 10:43 ` Aditya Kumar Singh
2024-01-30 13:50 ` Aditya Kumar Singh
2024-01-30 13:51 ` Johannes Berg
2024-01-30 4:32 ` [PATCH v7 4/5] wifi: mac80211: start and finalize channel switch on " Aditya Kumar Singh
2024-01-30 4:32 ` [PATCH v7 5/5] wifi: mac80211: add support to call csa_finish on a link Aditya Kumar Singh
2024-01-30 10:21 ` Johannes Berg
2024-01-30 10:53 ` Aditya Kumar Singh
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=c3ce6010-5cd2-4693-a43c-c89947cdb047@quicinc.com \
--to=quic_adisi@quicinc.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@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).