From: Kalle Valo <kvalo@kernel.org>
To: Maharaja Kennadyrajan <quic_mkenna@quicinc.com>
Cc: <ath11k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 1/2] ath11k: Relocate the func ath11k_mac_bitrate_mask_num_ht_rates() and change hweight16 to hweight8
Date: Thu, 11 May 2023 13:11:52 +0300 [thread overview]
Message-ID: <877ctfnpnb.fsf@kernel.org> (raw)
In-Reply-To: <a409ded2-f6e5-bc74-3fdb-231a92d9bde5@quicinc.com> (Maharaja Kennadyrajan's message of "Wed, 10 May 2023 15:35:20 +0530")
Maharaja Kennadyrajan <quic_mkenna@quicinc.com> writes:
> Ignore this patchset, I have sent the v2 version of this patchset by
> rebasing it on latest TOT.
Why? I had already applied v1 to the pending branch without issues:
https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/commit/?h=pending&id=e3fd9d322448ee29c65a30e9bedaed222d7548b9
https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/commit/?h=pending&id=b7c3ee0ddc2bf3ecf511793aa55622a9aa62e420
Is there a reason why I should take v2 instead?
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@kernel.org>
To: Maharaja Kennadyrajan <quic_mkenna@quicinc.com>
Cc: <ath11k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 1/2] ath11k: Relocate the func ath11k_mac_bitrate_mask_num_ht_rates() and change hweight16 to hweight8
Date: Thu, 11 May 2023 13:11:52 +0300 [thread overview]
Message-ID: <877ctfnpnb.fsf@kernel.org> (raw)
In-Reply-To: <a409ded2-f6e5-bc74-3fdb-231a92d9bde5@quicinc.com> (Maharaja Kennadyrajan's message of "Wed, 10 May 2023 15:35:20 +0530")
Maharaja Kennadyrajan <quic_mkenna@quicinc.com> writes:
> Ignore this patchset, I have sent the v2 version of this patchset by
> rebasing it on latest TOT.
Why? I had already applied v1 to the pending branch without issues:
https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/commit/?h=pending&id=e3fd9d322448ee29c65a30e9bedaed222d7548b9
https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/commit/?h=pending&id=b7c3ee0ddc2bf3ecf511793aa55622a9aa62e420
Is there a reason why I should take v2 instead?
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-05-11 10:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 9:20 [PATCH 1/2] ath11k: Relocate the func ath11k_mac_bitrate_mask_num_ht_rates() and change hweight16 to hweight8 Maharaja Kennadyrajan
2023-05-04 9:20 ` Maharaja Kennadyrajan
2023-05-04 9:20 ` [PATCH 2/2] ath11k: Send HT fixed rate in WMI peer fixed param Maharaja Kennadyrajan
2023-05-04 9:20 ` Maharaja Kennadyrajan
2023-05-10 10:05 ` [PATCH 1/2] ath11k: Relocate the func ath11k_mac_bitrate_mask_num_ht_rates() and change hweight16 to hweight8 Maharaja Kennadyrajan
2023-05-10 10:05 ` Maharaja Kennadyrajan
2023-05-11 10:11 ` Kalle Valo [this message]
2023-05-11 10:11 ` Kalle Valo
2023-05-11 10:15 ` Maharaja Kennadyrajan
2023-05-11 10:15 ` Maharaja Kennadyrajan
2023-05-17 8:19 ` Kalle Valo
2023-05-17 8:19 ` Kalle Valo
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=877ctfnpnb.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_mkenna@quicinc.com \
/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.