From: Kalle Valo <kvalo@codeaurora.org>
To: Lorenzo Bianconi <lorenzo@kernel.org>
Cc: linux-wireless@vger.kernel.org, kuba@kernel.org, nbd@nbd.name,
lorenzo.bianconi@redhat.com
Subject: Re: [PATCH wireless-drivers] mt76: dma: do not report truncated frames to mac80211
Date: Mon, 08 Feb 2021 10:32:40 +0200 [thread overview]
Message-ID: <87im735593.fsf@codeaurora.org> (raw)
In-Reply-To: <20210208082516.GB2593@lore-desk> (Lorenzo Bianconi's message of "Mon, 8 Feb 2021 09:25:16 +0100")
Lorenzo Bianconi <lorenzo@kernel.org> writes:
>> Lorenzo Bianconi <lorenzo@kernel.org> writes:
>>
>> > If the fragment is discarded in mt76_add_fragment() since shared_info
>> > frag array is full, discard truncated frames and do not forward them to
>> > mac80211.
>> >
>> > Signed-off-by: Lorenzo Bianconi <lorenzo@kernel.org>
>>
>> Should there be a Fixes line? I can add it.
>
> I am not sure it needs a Fixes tag.
I think the commit log should have some kind of description about the
background of the issue, for example if this is a recent regression or
has been there forever etc.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2021-02-08 8:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-07 11:48 [PATCH wireless-drivers] mt76: dma: do not report truncated frames to mac80211 Lorenzo Bianconi
2021-02-08 6:29 ` Kalle Valo
2021-02-08 8:25 ` Lorenzo Bianconi
2021-02-08 8:32 ` Kalle Valo [this message]
2021-02-08 11:20 ` Lorenzo Bianconi
2021-02-08 13:26 ` Kalle Valo
2021-02-08 13:32 ` Lorenzo Bianconi
2021-02-26 10:24 ` Lorenzo Bianconi
2021-02-26 10:58 ` Kalle Valo
2021-02-26 11:50 ` [wireless-drivers] " 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=87im735593.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=kuba@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=lorenzo@kernel.org \
--cc=nbd@nbd.name \
/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).