From: Kalle Valo <kvalo@kernel.org>
To: Dmitry Antipov <dmantipov@yandex.ru>
Cc: Ping-Ke Shih <pkshih@realtek.com>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/2] [v3] wifi: rtw89: cleanup private data structures
Date: Tue, 13 Jun 2023 12:12:03 +0300 [thread overview]
Message-ID: <877cs7enfg.fsf@kernel.org> (raw)
In-Reply-To: <975dee84-fa8f-1dbd-a2b8-2aba5a880b60@yandex.ru> (Dmitry Antipov's message of "Tue, 13 Jun 2023 11:56:24 +0300")
Dmitry Antipov <dmantipov@yandex.ru> writes:
> On 6/13/23 11:38, Kalle Valo wrote:
>
>> Failed to build
>
> Hmm... works for me against upstream at fb054096aea0 using following configuration:
>
> CONFIG_RTW89=m
> CONFIG_RTW89_CORE=m
> CONFIG_RTW89_PCI=m
> CONFIG_RTW89_8852A=m
> CONFIG_RTW89_8852B=m
> CONFIG_RTW89_8852C=m
> CONFIG_RTW89_8852AE=m
> CONFIG_RTW89_8852BE=m
> CONFIG_RTW89_8852CE=m
> CONFIG_RTW89_DEBUG=y
> CONFIG_RTW89_DEBUGMSG=y
> CONFIG_RTW89_DEBUGFS=y
You should use wireless-next as the baseline for wireless patches:
https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git/
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-06-13 9:12 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 8:33 [PATCH] wifi: rtw89: cleanup private data structures Dmitry Antipov
2023-06-06 14:08 ` [PATCH 1/2] " Dmitry Antipov
2023-06-06 14:08 ` [PATCH 2/2] wifi: rtw89: cleanup rtw89_iqk_info and related code Dmitry Antipov
2023-06-08 0:40 ` Ping-Ke Shih
2023-06-08 7:45 ` [PATCH] [v2] " Dmitry Antipov
2023-06-08 8:03 ` Ping-Ke Shih
2023-06-08 8:24 ` [PATCH 1/2] [v3] wifi: rtw89: cleanup private data structures Dmitry Antipov
2023-06-08 8:24 ` [PATCH 2/2] [v3] wifi: rtw89: cleanup rtw89_iqk_info and related code Dmitry Antipov
2023-06-08 8:42 ` Ping-Ke Shih
2023-06-13 8:23 ` Kalle Valo
2023-06-08 8:41 ` [PATCH 1/2] [v3] wifi: rtw89: cleanup private data structures Ping-Ke Shih
2023-06-13 8:38 ` Kalle Valo
2023-06-13 8:56 ` Dmitry Antipov
2023-06-13 9:11 ` Ping-Ke Shih
2023-06-13 9:12 ` Kalle Valo [this message]
2023-06-13 10:01 ` [PATCH 1/3] [v4] " Dmitry Antipov
2023-06-13 10:01 ` [PATCH 2/3] [v4] wifi: rtw89: cleanup rtw89_iqk_info and related code Dmitry Antipov
2023-06-14 2:54 ` Ping-Ke Shih
2023-06-13 10:01 ` [PATCH 3/3] wifi: rtw89: fix typo Dmitry Antipov
2023-06-14 2:56 ` Ping-Ke Shih
2023-06-14 5:11 ` [PATCH 1/3] [v5] wifi: rtw89: cleanup private data structures Dmitry Antipov
2023-06-14 5:11 ` [PATCH 2/3] [v5] wifi: rtw89: cleanup rtw89_iqk_info and related code Dmitry Antipov
2023-06-14 7:05 ` Ping-Ke Shih
2023-06-14 5:11 ` [PATCH 3/3] [v5] wifi: rtw89: fix spelling typo of IQK debug messages Dmitry Antipov
2023-06-14 7:06 ` Ping-Ke Shih
2023-06-14 8:15 ` [PATCH 1/3] [v6] wifi: rtw89: cleanup private data structures Dmitry Antipov
2023-06-14 8:15 ` [PATCH 2/3] [v6] wifi: rtw89: cleanup rtw89_iqk_info and related code Dmitry Antipov
2023-06-14 8:15 ` [PATCH 3/3] [v6] wifi: rtw89: fix spelling typo of IQK debug messages Dmitry Antipov
2023-06-14 8:22 ` Ping-Ke Shih
2023-06-15 7:47 ` [PATCH 1/3] [v6] wifi: rtw89: cleanup private data structures Kalle Valo
2023-06-14 7:04 ` [PATCH 1/3] [v5] " Ping-Ke Shih
2023-06-14 2:50 ` [PATCH 1/3] [v4] " Ping-Ke Shih
2023-06-08 0:31 ` [PATCH 1/2] " Ping-Ke Shih
2023-06-08 0:23 ` [PATCH] " Ping-Ke Shih
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=877cs7enfg.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=dmantipov@yandex.ru \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.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;
as well as URLs for NNTP newsgroup(s).