linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arend van Spriel <arend@broadcom.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	Hante Meuleman <meuleman@broadcom.com>
Subject: Re: [1/9] brcmfmac: Add support for the BCM4359 11ac RSDB PCIE device.
Date: Mon, 30 Nov 2015 12:59:35 +0100	[thread overview]
Message-ID: <565C3A27.4020903@broadcom.com> (raw)
In-Reply-To: <87fuznka81.fsf@kamboji.qca.qualcomm.com>

On 11/30/2015 12:17 PM, Kalle Valo wrote:
> Arend van Spriel <arend@broadcom.com> writes:
>
>> Actually, the patch above should have been submitted to
>> wireless-drivers as it solves a suspend/hibernate issue with 4350
>> device which we added in 4.4.
>
> Just to avoid any confusion you are meaning this commit:
>
> c2a43a6ba5e5 brcmfmac: Use new methods for pcie Power Management.
>
>> How should I handle that? This is what I was thinking:
>>
>> 1. submit revert for wireless-drivers-next.
>> 2. submit patch of c2a43a6ba5e5 for wireless-drivers.
>
> That's just messy and would prefer to avoid that. I think the best would
> be that you send the patch to 4.4-stable queue once the commit goes to
> Linus' tree during the next merge window. That way you get the fix to
> first 4.4.x stable releases. But not sure if it's eligible for a stable
> fix.
>
> BTW, I recommend sending patches to -rc release separately from the rest
> and marking them with intended the release number like "[PATCH 4.4]".
> That way it's clear for me to which tree you would like me to apply the
> patch.

We do that but not very often so probably did not happen in your 
maintainer period (yet).

Regards,
Arend

  reply	other threads:[~2015-11-30 11:59 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-29 19:33 [PATCH 0/9] brcmfmac: new device support and cleanup Arend van Spriel
2015-10-29 19:33 ` [PATCH 1/9] brcmfmac: Add support for the BCM4359 11ac RSDB PCIE device Arend van Spriel
2015-11-26 11:57   ` [1/9] " Kalle Valo
2015-11-27  8:59     ` Arend van Spriel
2015-11-30 11:17       ` Kalle Valo
2015-11-30 11:59         ` Arend van Spriel [this message]
2015-10-29 19:33 ` [PATCH 2/9] brcmfmac: Simplify and fix usage of brcmf_ifname Arend van Spriel
2015-10-29 19:33 ` [PATCH 3/9] brcmfmac: Remove unnecessary check from start_xmit Arend van Spriel
2015-10-29 19:33 ` [PATCH 4/9] brcmfmac: Remove unncessary variable irq_requested Arend van Spriel
2015-10-29 19:33 ` [PATCH 5/9] brcmfmac: Disable runtime pm for USB Arend van Spriel
2015-10-29 19:33 ` [PATCH 6/9] brcmfmac: Add RSDB support Arend van Spriel
2015-11-12 19:49   ` Kalle Valo
2015-11-13  9:11     ` Arend van Spriel
2015-11-13  9:29       ` Kalle Valo
2015-10-29 19:33 ` [PATCH 7/9] brcmfmac: Use consistent naming for bsscfgidx Arend van Spriel
2015-10-29 19:33 ` [PATCH 8/9] brcmfmac: Use new methods for pcie Power Management Arend van Spriel
2015-10-29 19:33 ` [PATCH 9/9] brcmfmac: Add wowl wake indication report Arend van Spriel
2015-10-29 19:49 ` [PATCH 0/9] brcmfmac: new device support and cleanup Kalle Valo
2015-10-29 20:00   ` 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=565C3A27.4020903@broadcom.com \
    --to=arend@broadcom.com \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=meuleman@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 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).