From: Kalle Valo <kvalo@codeaurora.org>
To: Arend van Spriel <arend.vanspriel@broadcom.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [1/7] brcmfmac: handle FWHALT mailbox indication
Date: Wed, 08 Nov 2017 14:05:33 +0200 [thread overview]
Message-ID: <8760algelu.fsf@codeaurora.org> (raw)
In-Reply-To: <5A02DCC0.8000406@broadcom.com> (Arend van Spriel's message of "Wed, 8 Nov 2017 11:30:24 +0100")
Arend van Spriel <arend.vanspriel@broadcom.com> writes:
> 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/
That's not pending, it's in "Changes Requested" meaning that I have
dropped them:
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches#checking_state_of_patches_from_patchwork
"Deferred" is the state when patch is pending an action from me. Yes,
patchwork state names suck :)
> 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.
To keep things simple I would prefer you resubmit them. I'm at Netdev
2.2 right now so on a quite tight schedule to get everything ready
before the weekend when the merge window opens.
--
Kalle Valo
next prev parent reply other threads:[~2017-11-08 12:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 10:30 [1/7] brcmfmac: handle FWHALT mailbox indication Arend van Spriel
2017-11-08 12:05 ` Kalle Valo [this message]
-- 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=8760algelu.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=arend.vanspriel@broadcom.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 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).