From: Bob Copeland <me@bobcopeland.com>
To: Arend van Spriel <arend.vanspriel@broadcom.com>
Cc: Kalle Valo <kvalo@codeaurora.org>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH for-4.13] brcmfmac: fix regression in brcmf_sdio_txpkt_hdalign()
Date: Wed, 12 Jul 2017 10:29:01 -0400 [thread overview]
Message-ID: <20170712142901.evso24vh3jfj6umk@localhost> (raw)
In-Reply-To: <1499851968-18768-1-git-send-email-arend.vanspriel@broadcom.com>
On Wed, Jul 12, 2017 at 10:32:48AM +0100, Arend van Spriel wrote:
> Recent change in brcmf_sdio_txpkt_hdalign() changed the
> behavior and now always returns 0. This resulted in a
> regression which basically renders the device useless.
Should this go via netdev as well, or just wait for Kalle (returning
on Sunday)?
--
Bob Copeland %% https://bobcopeland.com/
next prev parent reply other threads:[~2017-07-12 14:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 9:32 [PATCH for-4.13] brcmfmac: fix regression in brcmf_sdio_txpkt_hdalign() Arend van Spriel
2017-07-12 14:29 ` Bob Copeland [this message]
2017-07-12 14:57 ` Arend van Spriel
2017-07-21 7:41 ` [for-4.13] " Kalle Valo
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=20170712142901.evso24vh3jfj6umk@localhost \
--to=me@bobcopeland.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox