From: Kalle Valo <kvalo@kernel.org>
To: Jeff Johnson <quic_jjohnson@quicinc.com>
Cc: Dmitry Antipov <dmantipov@yandex.ru>,
Ziyang Huang <hzyitc@outlook.com>,
<linux-wireless@vger.kernel.org>, <ath11k@lists.infradead.org>
Subject: Re: [PATCH] wifi: ath11k: simplify ath11k_mac_validate_vht_he_fixed_rate_settings()
Date: Thu, 27 Jul 2023 19:33:00 +0300 [thread overview]
Message-ID: <87h6ppz54z.fsf@kernel.org> (raw)
In-Reply-To: <b23c9ebe-b49b-0c8c-5e20-d02fd4134844@quicinc.com> (Jeff Johnson's message of "Wed, 26 Jul 2023 11:31:12 -0700")
Jeff Johnson <quic_jjohnson@quicinc.com> writes:
> On 7/26/2023 2:21 AM, Dmitry Antipov wrote:
>
>> In 'ath11k_mac_validate_vht_he_fixed_rate_settings()', 'ar->ab->peers'
>> list is not altered so 'list_for_each_entry()' should be safe.
>> Signed-off-by: Dmitry Antipov <dmantipov@yandex.ru>
>
> In the future please make sure driver-specific mailing lists are
> included in your patches when they exist in the MAINTAINERS file.
> Adding ath11k@lists.infradead.org
And this is actually v2, there was already v1 sent earlier this month:
https://patchwork.kernel.org/project/linux-wireless/patch/20230704174753.76968-1-dmantipov@yandex.ru/
Dmitry, PLEASE read our documentation from the wiki below. You need to
always mark the patch as v2 and provide a changelog what changed since
v1.
And especially slow down with the rate of patches you are submitting and
instead use that time to learn the process first.
--
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: Jeff Johnson <quic_jjohnson@quicinc.com>
Cc: Dmitry Antipov <dmantipov@yandex.ru>,
Ziyang Huang <hzyitc@outlook.com>,
<linux-wireless@vger.kernel.org>, <ath11k@lists.infradead.org>
Subject: Re: [PATCH] wifi: ath11k: simplify ath11k_mac_validate_vht_he_fixed_rate_settings()
Date: Thu, 27 Jul 2023 19:33:00 +0300 [thread overview]
Message-ID: <87h6ppz54z.fsf@kernel.org> (raw)
In-Reply-To: <b23c9ebe-b49b-0c8c-5e20-d02fd4134844@quicinc.com> (Jeff Johnson's message of "Wed, 26 Jul 2023 11:31:12 -0700")
Jeff Johnson <quic_jjohnson@quicinc.com> writes:
> On 7/26/2023 2:21 AM, Dmitry Antipov wrote:
>
>> In 'ath11k_mac_validate_vht_he_fixed_rate_settings()', 'ar->ab->peers'
>> list is not altered so 'list_for_each_entry()' should be safe.
>> Signed-off-by: Dmitry Antipov <dmantipov@yandex.ru>
>
> In the future please make sure driver-specific mailing lists are
> included in your patches when they exist in the MAINTAINERS file.
> Adding ath11k@lists.infradead.org
And this is actually v2, there was already v1 sent earlier this month:
https://patchwork.kernel.org/project/linux-wireless/patch/20230704174753.76968-1-dmantipov@yandex.ru/
Dmitry, PLEASE read our documentation from the wiki below. You need to
always mark the patch as v2 and provide a changelog what changed since
v1.
And especially slow down with the rate of patches you are submitting and
instead use that time to learn the process first.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-07-27 17:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 9:21 [PATCH] wifi: ath11k: simplify ath11k_mac_validate_vht_he_fixed_rate_settings() Dmitry Antipov
2023-07-26 18:31 ` Jeff Johnson
2023-07-26 18:31 ` Jeff Johnson
2023-07-27 16:33 ` Kalle Valo [this message]
2023-07-27 16:33 ` Kalle Valo
2023-08-02 11:52 ` 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=87h6ppz54z.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=dmantipov@yandex.ru \
--cc=hzyitc@outlook.com \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_jjohnson@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.