From: lucid_duck@justthetip.ca
To: "Felix Baumann" <felix.baumann@freifunk-aachen.de>
Cc: linux-mediatek@lists.infradead.org,
linux-wireless@vger.kernel.org, lorenzo.bianconi@redhat.com,
morrownr@gmail.com, nbd@nbd.name, satadru@gmail.com,
sean.wang@kernel.org, jonas.gorski@gmail.com
Subject: Re: [PATCH 1/3] wifi: mt76: connac: use a helper to cache txpower_cur
Date: Tue, 31 Mar 2026 16:41:24 +0000 [thread overview]
Message-ID: <630ad945be38b7a97ffbb2a02524b7728c9efcb7@justthetip.ca> (raw)
In-Reply-To: <3f4103d9-4871-4ae8-93a7-d286fce37443@freifunk-aachen.de>
Hi Felix,
Thank you, and thanks for reaching out.
Yes, absolutely -- my real name is Devin Wittmayer.
Sean is welcome to use it for the Co-developed-by tag.
Cheers,
Devin
March 31, 2026 at 12:59 AM, "Felix Baumann" <felix.baumann@freifunk-aachen.de> wrote:
>
> Hi Lucid Duck,
>
> thanks a lot for your contribution. Very much appreciated :)
> The kernel has a strict policy for contributions: real names only.
> https://www.kernel.org/doc/html/v4.11/process/submitting-patches.html#sign-your-work-the-developer-s-certificate-of-origin
>
> May I kindly ask whether it would be okay for Sean to use your real name?
> https://github.com/Lucid-Duck
>
> --
> Regards
> Felix Baumann
>
prev parent reply other threads:[~2026-03-31 16:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 4:33 [PATCH 1/3] wifi: mt76: connac: use a helper to cache txpower_cur Sean Wang
2026-03-25 4:33 ` [PATCH 2/3] wifi: mt76: connac: factor out rate power limit calculation Sean Wang
2026-03-25 4:33 ` [PATCH 3/3] wifi: mt76: mt792x: report txpower for the requested vif link Sean Wang
2026-03-26 17:04 ` [PATCH 1/3] wifi: mt76: connac: use a helper to cache txpower_cur Lucid Duck
2026-03-27 0:23 ` Sean Wang
2026-03-27 2:15 ` Lucid Duck
2026-03-31 7:59 ` Felix Baumann
2026-03-31 9:30 ` Jonas Gorski
2026-03-31 16:41 ` lucid_duck [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=630ad945be38b7a97ffbb2a02524b7728c9efcb7@justthetip.ca \
--to=lucid_duck@justthetip.ca \
--cc=felix.baumann@freifunk-aachen.de \
--cc=jonas.gorski@gmail.com \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=morrownr@gmail.com \
--cc=nbd@nbd.name \
--cc=satadru@gmail.com \
--cc=sean.wang@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