public inbox for ath12k@lists.infradead.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Wen Gong <quic_wgong@quicinc.com>
Cc: <ath12k@lists.infradead.org>
Subject: Re: ath12k-check warnings
Date: Wed, 27 Sep 2023 10:09:21 +0300	[thread overview]
Message-ID: <87bkdo853y.fsf@kernel.org> (raw)
In-Reply-To: <87o7hp8s0l.fsf@kernel.org> (Kalle Valo's message of "Tue, 26 Sep 2023 07:42:18 +0300")

Kalle Valo <kvalo@kernel.org> writes:

>> /home/wgong/opensource/kernel/ath/./ath12k-check:32:
>> DeprecationWarning: The distutils package is deprecated and slated for
>> removal in Python 3.12. Use setuptools or check PEP 632 for potential
>> alternatives
>>   import distutils.spawn
>
> I don't see this warning on Debian 12 but I'll need to fix that as well.
> But this is what I hate with python, they are always depracating
> something and it's extra work for us.

I fixed this now:

https://github.com/qca/qca-swiss-army-knife/commit/2bd53768fa273f78ed044aee9ac88daf2ccc1682

Please let me know if you still see warnings from ath12k-check or
ath11k-check. With ath.git master branch you should get no warnings,
otherwise something is wrong.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

-- 
ath12k mailing list
ath12k@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/ath12k

      reply	other threads:[~2023-09-27  7:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-24  2:54 [PATCH v2] wifi: ath12k: enable 320 MHz bandwidth for 6 GHz band in EHT PHY capbility for WCN7850 Wen Gong
2023-08-24  4:22 ` Jeff Johnson
2023-08-25  7:53 ` Kalle Valo
2023-08-28  6:09   ` Wen Gong
2023-09-06 14:04     ` ath12k-check warnings Kalle Valo
2023-09-26  2:32       ` Wen Gong
2023-09-26  4:42         ` Kalle Valo
2023-09-27  7:09           ` Kalle Valo [this message]

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=87bkdo853y.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=ath12k@lists.infradead.org \
    --cc=quic_wgong@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox