From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: RE: [1/7] brcmfmac: handle FWHALT mailbox indication
Date: Wed, 8 Nov 2017 11:30:24 +0100 [thread overview]
Message-ID: <5A02DCC0.8000406@broadcom.com> (raw)
Hi Kalle,
I was preparing a new patch series and got a bit confused. Turns out
there was a series still pending in patchwork.
https://patchwork.kernel.org/patch/9948825/
So I applied the pending series on wireless-drivers-next and it compiles
fine. So what I think happened is that the series depended on a patch
that was submitted to wireless-drivers at that time. Can these patches
be taken now or do I need to resubmit.
Regards,
Arend
next reply other threads:[~2017-11-08 10:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 10:30 Arend van Spriel [this message]
2017-11-08 12:05 ` [1/7] brcmfmac: handle FWHALT mailbox indication Kalle Valo
-- strict thread matches above, loose matches on Subject: below --
2017-09-12 9:22 [PATCH 1/7] " Arend van Spriel
2017-09-25 8:18 ` [1/7] " Kalle Valo
2017-09-25 9:26 ` James Hughes
2017-09-25 9:30 ` James Hughes
2017-09-26 11:11 ` Arend van Spriel
2017-09-26 12:05 ` James Hughes
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=5A02DCC0.8000406@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=kvalo@codeaurora.org \
--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.