From: Kalle Valo <kvalo@codeaurora.org>
To: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: nbd@nbd.name, dan.carpenter@oracle.com, linux-wireless@vger.kernel.org
Subject: Re: [1/2] mt76: fix possible NULL pointer dereferencing in mt76x2_ampdu_action()
Date: Mon, 8 Jan 2018 17:35:23 +0000 (UTC) [thread overview]
Message-ID: <20180108173523.A3D036077A@smtp.codeaurora.org> (raw)
In-Reply-To: <18a56326d68a7d53f3197e450cae0e28382d8d2c.1513252573.git.lorenzo.bianconi@redhat.com>
Lorenzo Bianconi <lorenzo.bianconi@redhat.com> wrote:
> Initialize mt76_txq pointer after ieee80211_txq pointer check.
> Remove space after the pointer cast
>
> Fixes: 7bc04215a66b ("mt76: add driver code for MT76x2e")
> Signed-off-by: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
What am I supposed to do with this and patch 2? Drop?
--
https://patchwork.kernel.org/patch/10111937/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2018-01-08 17:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-14 12:03 [PATCH 0/2] Fix two possible NULL pointer dereferencing issues Lorenzo Bianconi
2017-12-14 12:03 ` [PATCH 1/2] mt76: fix possible NULL pointer dereferencing in mt76x2_ampdu_action() Lorenzo Bianconi
2018-01-08 17:35 ` Kalle Valo [this message]
[not found] ` <20180108173523.B23C360B22@smtp.codeaurora.org>
2018-01-08 17:44 ` [1/2] " Lorenzo Bianconi
2018-01-08 18:16 ` Kalle Valo
2018-01-08 18:30 ` Lorenzo Bianconi
2018-01-17 10:26 ` Felix Fietkau
2018-01-17 14:50 ` Kalle Valo
2018-01-17 15:56 ` Sven Eckelmann
2018-01-23 5:14 ` Kalle Valo
2018-01-17 14:50 ` Kalle Valo
2017-12-14 12:03 ` [PATCH 2/2] mt76: fix possible NULL pointer dereferencing in mt76x2_mac_write_txwi() Lorenzo Bianconi
2017-12-14 15:30 ` [PATCH 0/2] Fix two possible NULL pointer dereferencing issues Felix Fietkau
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=20180108173523.A3D036077A@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=dan.carpenter@oracle.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--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).