All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: "Piotr Haber" <phaber@broadcom.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 3.9] brcmsmac: Fix merge issue
Date: Thu, 25 Apr 2013 22:15:53 +0200	[thread overview]
Message-ID: <51798EF9.9020803@broadcom.com> (raw)
In-Reply-To: <1366885629-11382-1-git-send-email-phaber@broadcom.com>

On 04/25/2013 12:27 PM, Piotr Haber wrote:
> Commit 7088f4835aa353f7226e57e73fd9e6564a4dfb75
> "Merge branch 'master' of
> git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless"
> ramoved call to brcms_led_unregister in mac80211_if.c
>

Hi Piotr,

After we discussed this, I realized that the led support was added to 
wireless-next, ie. for v3.10 kernel.

John,

Can you take it in wireless-next repository this close to the merge 
window? It applies without issues to that.

Regards,
Arend

> Reviewed-by: Hante Meuleman <meuleman@broadcom.com>
> Reviewed-by: Arend van Spriel <arend@broadcom.com>
> Signed-off-by: Piotr Haber <phaber@broadcom.com>
> ---
>   .../net/wireless/brcm80211/brcmsmac/mac80211_if.c  |    1 +
>   1 file changed, 1 insertion(+)
>
> diff --git a/drivers/net/wireless/brcm80211/brcmsmac/mac80211_if.c b/drivers/net/wireless/brcm80211/brcmsmac/mac80211_if.c
> index 2346821..3a65447 100644
> --- a/drivers/net/wireless/brcm80211/brcmsmac/mac80211_if.c
> +++ b/drivers/net/wireless/brcm80211/brcmsmac/mac80211_if.c
> @@ -336,6 +336,7 @@ static void brcms_remove(struct bcma_device *pdev)
>   	struct brcms_info *wl = hw->priv;
>
>   	if (wl->wlc) {
> +		brcms_led_unregister(wl);
>   		wiphy_rfkill_set_hw_state(wl->pub->ieee_hw->wiphy, false);
>   		wiphy_rfkill_stop_polling(wl->pub->ieee_hw->wiphy);
>   		ieee80211_unregister_hw(hw);
>



      reply	other threads:[~2013-04-25 20:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-25 10:27 [PATCH 3.9] brcmsmac: Fix merge issue Piotr Haber
2013-04-25 20:15 ` Arend van Spriel [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=51798EF9.9020803@broadcom.com \
    --to=arend@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=phaber@broadcom.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.