From: Kalle Valo <kvalo@kernel.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Arend van Spriel <aspriel@gmail.com>,
Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com,
SHA-cyfmac-dev-list@infineon.com
Subject: Re: [PATCH 1/2] brcmfmac: Add brcmf_c_set_cur_etheraddr() helper
Date: Tue, 26 Jul 2022 16:08:35 +0300 [thread overview]
Message-ID: <87sfmokomk.fsf@kernel.org> (raw)
In-Reply-To: <56fa5cfb-7f38-4380-67e5-ba362dd8e440@redhat.com> (Hans de Goede's message of "Fri, 8 Jul 2022 15:34:57 +0200")
Hans de Goede <hdegoede@redhat.com> writes:
> Hi,
>
> On 7/8/22 15:32, Hans de Goede wrote:
>> Add a little helper to send "cur_etheraddr" commands to the interface
>> and to handle the error reporting of it in a single place.
>>
>> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
>
> Ugh, I accidentally used Kalle's old address. I'll resend this with
> the right address, sorry for the duplicate emails.
No worries. And it actually doesn't even matter as I take the patches
directly from patchwork :)
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-07-26 13:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 13:32 [PATCH 1/2] brcmfmac: Add brcmf_c_set_cur_etheraddr() helper Hans de Goede
2022-07-08 13:32 ` [PATCH 2/2] brcmfmac: Replace default (not configured) MAC with a random MAC Hans de Goede
2022-07-08 13:34 ` [PATCH 1/2] brcmfmac: Add brcmf_c_set_cur_etheraddr() helper Hans de Goede
2022-07-26 13:08 ` Kalle Valo [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-08 13:37 Hans de Goede
2022-07-08 18:29 ` Arend Van Spriel
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=87sfmokomk.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=SHA-cyfmac-dev-list@infineon.com \
--cc=aspriel@gmail.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=hdegoede@redhat.com \
--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 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.