From: Jakub Kicinski <kuba@kernel.org>
To: Xiu Jianfeng <xiujianfeng@huawei.com>
Cc: <kvalo@kernel.org>, <davem@davemloft.net>, <edumazet@google.com>,
<pabeni@redhat.com>, <rmani@qti.qualcomm.com>,
<ath10k@lists.infradead.org>, <linux-wireless@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] wifi: ath10k: Fix return value in ath10k_pci_init()
Date: Wed, 9 Nov 2022 19:25:32 -0800 [thread overview]
Message-ID: <20221109192532.259e4af3@kernel.org> (raw)
In-Reply-To: <20221110031228.247361-1-xiujianfeng@huawei.com>
On Thu, 10 Nov 2022 11:12:28 +0800 Xiu Jianfeng wrote:
> To: <kvalo@kernel.org>, <davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>, <rmani@qti.qualcomm.com>
> CC: <ath10k@lists.infradead.org>, <linux-wireless@vger.kernel.org>, <linux-kernel@vger.kernel.org>
How did you come up with this CC list? If you're CCing netdev
maintainers you should also CC netdev@vger.kernel.org
Somehow you managed to CC LMKL but not netdev :S
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Xiu Jianfeng <xiujianfeng@huawei.com>
Cc: <kvalo@kernel.org>, <davem@davemloft.net>, <edumazet@google.com>,
<pabeni@redhat.com>, <rmani@qti.qualcomm.com>,
<ath10k@lists.infradead.org>, <linux-wireless@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] wifi: ath10k: Fix return value in ath10k_pci_init()
Date: Wed, 9 Nov 2022 19:25:32 -0800 [thread overview]
Message-ID: <20221109192532.259e4af3@kernel.org> (raw)
In-Reply-To: <20221110031228.247361-1-xiujianfeng@huawei.com>
On Thu, 10 Nov 2022 11:12:28 +0800 Xiu Jianfeng wrote:
> To: <kvalo@kernel.org>, <davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>, <rmani@qti.qualcomm.com>
> CC: <ath10k@lists.infradead.org>, <linux-wireless@vger.kernel.org>, <linux-kernel@vger.kernel.org>
How did you come up with this CC list? If you're CCing netdev
maintainers you should also CC netdev@vger.kernel.org
Somehow you managed to CC LMKL but not netdev :S
next prev parent reply other threads:[~2022-11-10 3:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 3:12 [PATCH v2] wifi: ath10k: Fix return value in ath10k_pci_init() Xiu Jianfeng
2022-11-10 3:12 ` Xiu Jianfeng
2022-11-10 3:25 ` Jakub Kicinski [this message]
2022-11-10 3:25 ` Jakub Kicinski
2022-11-10 4:00 ` xiujianfeng
2022-11-10 4:00 ` xiujianfeng
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=20221109192532.259e4af3@kernel.org \
--to=kuba@kernel.org \
--cc=ath10k@lists.infradead.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rmani@qti.qualcomm.com \
--cc=xiujianfeng@huawei.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.