From: Karthikeyan Periyasamy <quic_periyasa@quicinc.com>
To: Kalle Valo <kvalo@kernel.org>
Cc: <ath12k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] [RESEND] wifi: ath12k: refactor the link capable flag
Date: Wed, 3 Apr 2024 16:51:09 +0530 [thread overview]
Message-ID: <9200cdc1-00ae-d3bb-1f3d-abb4ce993cf7@quicinc.com> (raw)
In-Reply-To: <87o7aq68a3.fsf@kernel.org>
On 4/3/2024 4:08 PM, Kalle Valo wrote:
> Karthikeyan Periyasamy <quic_periyasa@quicinc.com> writes:
>
>> extend the link capable flag to accommodate inter-device capability.
>>
>> v2:
>> - Rename the terminology from chip to device
>>
>> Karthikeyan Periyasamy (2):
>> wifi: ath12k: extend the link capable flag
>> wifi: ath12k: fix link capable flags
>
> Why the resend?
I missed the version log in the commit message.
I'm not really a fan of these "RESEND" versions. If you
> need to resend something simply just increase the version number (in
> this case to v3) and explain in the change log why you sent v3. That's a
> lot more clear for everyone than having "v2", "v2 RESEND", "v2 RESEND
> RESEND" and what not. It's not like we are running out of version
> numbers ;)
>
> But no need to resend because of this :)
>
Sure, i got it.
--
Karthikeyan Periyasamy
--
கார்த்திகேயன் பெரியசாமி
next prev parent reply other threads:[~2024-04-03 11:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 4:20 [PATCH v2 0/2] [RESEND] wifi: ath12k: refactor the link capable flag Karthikeyan Periyasamy
2024-04-03 4:20 ` [PATCH v2 1/2] [RESEND] wifi: ath12k: extend " Karthikeyan Periyasamy
2024-04-03 19:29 ` Jeff Johnson
2024-04-05 12:57 ` Kalle Valo
2024-04-08 14:38 ` Kalle Valo
2024-04-03 4:20 ` [PATCH v2 2/2] [RESEND] wifi: ath12k: fix link capable flags Karthikeyan Periyasamy
2024-04-03 19:29 ` Jeff Johnson
2024-04-03 10:38 ` [PATCH v2 0/2] [RESEND] wifi: ath12k: refactor the link capable flag Kalle Valo
2024-04-03 11:21 ` Karthikeyan Periyasamy [this message]
2024-04-03 15:00 ` Jeff Johnson
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=9200cdc1-00ae-d3bb-1f3d-abb4ce993cf7@quicinc.com \
--to=quic_periyasa@quicinc.com \
--cc=ath12k@lists.infradead.org \
--cc=kvalo@kernel.org \
--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