From: Lorenzo Bianconi <lorenzo@kernel.org>
To: Felix Fietkau <nbd@nbd.name>
Cc: linux-wireless@vger.kernel.org, lorenzo.bianconi@redhat.com,
ryder.lee@mediatek.com, royluo@google.com
Subject: Re: [PATCH 1/3] mt76: mt76x02: fix coverage_class type
Date: Wed, 20 Nov 2019 13:37:23 +0200 [thread overview]
Message-ID: <20191120113723.GA21993@localhost.localdomain> (raw)
In-Reply-To: <a6f5e59e-533a-644e-895c-e81440a7ca6e@nbd.name>
[-- Attachment #1: Type: text/plain, Size: 499 bytes --]
> On 2019-11-15 16:05, Lorenzo Bianconi wrote:
> > Fix coverage_class definition in mt76x02_dev data structure since
> > coverage_class can be negative to enable dynack (just supported by
> > ath9k)
> >
> > Fixes: 7bc04215a66b ("mt76: add driver code for MT76x2e")
> > Signed-off-by: Lorenzo Bianconi <lorenzo@kernel.org>
> I'd prefer a patch that sets the internal coverage_class field value to
> 0 for negative input values.
ack, I will do in v2
Regards,
Lorenzo
>
> - Felix
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2019-11-20 11:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 15:05 [PATCH 0/3] add set_coverage support to mt7615 driver Lorenzo Bianconi
2019-11-15 15:05 ` [PATCH 1/3] mt76: mt76x02: fix coverage_class type Lorenzo Bianconi
2019-11-20 11:24 ` Felix Fietkau
2019-11-20 11:37 ` Lorenzo Bianconi [this message]
2019-11-15 15:05 ` [PATCH 2/3] mt76: move coverage_class and slottime in mt76_dev Lorenzo Bianconi
2019-11-20 11:20 ` Felix Fietkau
2019-11-20 11:42 ` Lorenzo Bianconi
2019-11-20 11:44 ` Felix Fietkau
2019-11-15 15:05 ` [PATCH 3/3] mt76: mt7615: add set_coverage class support Lorenzo Bianconi
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=20191120113723.GA21993@localhost.localdomain \
--to=lorenzo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=nbd@nbd.name \
--cc=royluo@google.com \
--cc=ryder.lee@mediatek.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 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.