From: Lorenzo Bianconi <lorenzo@kernel.org>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: linux-wireless@vger.kernel.org, Felix Fietkau <nbd@nbd.name>,
Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Subject: Re: [PATCH 0/3] mt76: usb: alignment and endianes improvements
Date: Thu, 4 Jul 2019 00:12:45 +0200 [thread overview]
Message-ID: <20190703221245.GA23584@localhost.localdomain> (raw)
In-Reply-To: <1562079961-15527-1-git-send-email-sgruszka@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 792 bytes --]
> Fix endian bug and do some minor optimizations in mt76u_{copy,rr,wr} .
>
> I do not mark cc stable endian fix as noboby reported this issue,
> i.e. use the driver on big endian machine, but make it a separate patch,
> so it can be backported if needed.
>
Tested-by: Lorenzo Bianconi <lorenzo@kernel.org>
> This is on top of:
> [PATCH] mt76: round up length on mt76_wr_copy
>
> Stanislaw Gruszka (3):
> mt76: usb: fix endian in mt76u_copy
> mt76: usb: remove unneeded {put,get}_unaligned
> mt76: usb: use full intermediate buffer in mt76u_copy
>
> drivers/net/wireless/mediatek/mt76/mt76.h | 5 ++++-
> drivers/net/wireless/mediatek/mt76/usb.c | 27 ++++++++++++++++-----------
> 2 files changed, 20 insertions(+), 12 deletions(-)
>
> --
> 1.9.3
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2019-07-03 22:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-02 15:05 [PATCH 0/3] mt76: usb: alignment and endianes improvements Stanislaw Gruszka
2019-07-02 15:05 ` [PATCH 1/3] mt76: usb: fix endian in mt76u_copy Stanislaw Gruszka
2019-07-09 10:06 ` Stanislaw Gruszka
2019-07-02 15:06 ` [PATCH 2/3] mt76: usb: remove unneeded {put,get}_unaligned Stanislaw Gruszka
2019-07-02 15:06 ` [PATCH 3/3] mt76: usb: use full intermediate buffer in mt76u_copy Stanislaw Gruszka
2019-07-09 10:12 ` Stanislaw Gruszka
2019-07-09 13:45 ` Felix Fietkau
2019-07-03 22:12 ` Lorenzo Bianconi [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=20190703221245.GA23584@localhost.localdomain \
--to=lorenzo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=nbd@nbd.name \
--cc=sgruszka@redhat.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).