From: Kalle Valo <kvalo@codeaurora.org>
To: Lubomir Rintel <lkundrak@v3.sk>
Cc: Steve deRosier <derosier@cal-sierra.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
Lubomir Rintel <lkundrak@v3.sk>
Subject: Re: [PATCH v2 1/3] libertas_tf: move hardware callbacks to a separate structure
Date: Wed, 20 Feb 2019 17:56:13 +0000 (UTC) [thread overview]
Message-ID: <20190220175613.9A9DA608EA@smtp.codeaurora.org> (raw)
In-Reply-To: <20190220105840.793525-2-lkundrak@v3.sk>
Lubomir Rintel <lkundrak@v3.sk> wrote:
> We'll need to talk to the firmware to get a hardware address before
> device is registered with ieee80211 subsystem at the end of
> lbtf_add_card(). Hooking the callbacks after that is too late.
>
> Signed-off-by: Lubomir Rintel <lkundrak@v3.sk>
3 patches applied to wireless-drivers-next.git, thanks.
be9d0d3fe139 libertas_tf: move hardware callbacks to a separate structure
baa0280f08c7 libertas_tf: don't defer firmware loading until start()
5d04b22b881d libertas_tf: get the MAC address before registering the device
--
https://patchwork.kernel.org/patch/10821819/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2019-02-20 17:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 10:58 [PATCH v2 0/3] libertas_tf: fix setting the hardware address] Lubomir Rintel
2019-02-20 10:58 ` [PATCH v2 1/3] libertas_tf: move hardware callbacks to a separate structure Lubomir Rintel
2019-02-20 17:56 ` Kalle Valo [this message]
2019-02-20 10:58 ` [PATCH v2 2/3] libertas_tf: don't defer firmware loading until start() Lubomir Rintel
2019-02-20 10:58 ` [PATCH v2 3/3] libertas_tf: get the MAC address before registering the device Lubomir Rintel
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=20190220175613.9A9DA608EA@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=derosier@cal-sierra.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lkundrak@v3.sk \
/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
Powered by JetHome