From: Kalle Valo <kvalo@codeaurora.org>
To: cjhuang@codeaurora.org
Cc: ath11k@lists.infradead.org, briannorris@chromium.org,
linux-wireless@vger.kernel.org, dianders@chromium.org
Subject: Re: [RFC 1/2] nl80211: add common API to configure SAR power limitations.
Date: Tue, 22 Sep 2020 11:09:22 +0300 [thread overview]
Message-ID: <87sgbaz0zx.fsf@codeaurora.org> (raw)
In-Reply-To: <f98b45b6c035085fe15c9abf16b4c0b5@codeaurora.org> (cjhuang@codeaurora.org's message of "Tue, 22 Sep 2020 13:47:24 +0800")
cjhuang@codeaurora.org writes:
> Sorry, send to wrong ath11k list.
> Let me resend to ath10k list for these 2 patches.
When you submit a new version mark it as "v2". Otherwise people don't
know what's the latest version.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2020-09-22 8:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 5:36 [RFC 1/2] nl80211: add common API to configure SAR power limitations Carl Huang
2020-09-22 5:36 ` [RFC 2/2] ath10k: allow dynamic SAR power limits via common API Carl Huang
2020-09-22 5:47 ` [RFC 1/2] nl80211: add common API to configure SAR power limitations cjhuang
2020-09-22 8:09 ` Kalle Valo [this message]
2020-11-04 2:00 ` Brian Norris
2020-11-04 7:32 ` Carl Huang
2020-11-04 17:44 ` Brian Norris
2020-11-05 8:35 ` Kalle Valo
2020-11-05 11:10 ` Carl Huang
2020-11-05 18:25 ` Brian Norris
2020-11-06 10:11 ` Carl Huang
2020-11-05 11:17 ` Carl Huang
-- strict thread matches above, loose matches on Subject: below --
2020-09-22 5:49 Carl Huang
2020-09-28 12:36 ` Johannes Berg
2020-10-30 20:56 ` Abhishek Kumar
2020-10-31 2:46 ` Abhishek Kumar
2020-11-03 2:34 ` Carl Huang
2020-11-03 13:15 ` Johannes Berg
2020-11-04 1:17 ` Abhishek Kumar
2020-11-04 6:18 ` Carl Huang
2020-11-04 8:44 ` Carl Huang
2020-11-04 17:48 ` Brian Norris
2020-11-05 11:37 ` Carl Huang
2020-11-04 23:18 ` Brian Norris
2020-11-04 23:27 ` Brian Norris
2020-11-05 11:30 ` Carl Huang
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=87sgbaz0zx.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=briannorris@chromium.org \
--cc=cjhuang@codeaurora.org \
--cc=dianders@chromium.org \
--cc=linux-wireless@vger.kernel.org \
/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).