From: Sven Eckelmann <sven@narfation.org>
To: Kalle Valo <kvalo@codeaurora.org>, linux-wireless@vger.kernel.org
Subject: Re: [1/2] mt76: fix possible NULL pointer dereferencing in mt76x2_ampdu_action()
Date: Wed, 17 Jan 2018 16:56:46 +0100 [thread overview]
Message-ID: <9978263.24XfVAzbPX@bentobox> (raw)
In-Reply-To: <87o9lsczf4.fsf@kamboji.qca.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 562 bytes --]
On Mittwoch, 17. Januar 2018 16:50:23 CET Kalle Valo wrote:
[...]
> >> I didn't see Felix's ack, at least not on patchwork.
> >
> > I sent my ack (for both patches) as a reply to 0/2
>
> Ah. patchwork is annoying as it doesn't show the cover letter at all so
> I missed that.
Newer version at least can track the series and their cover letters. This is
not completely what you want but at least there is hope. Here is an example:
https://patchwork.open-mesh.org/cover/17240/ (you can use "Related" to see all
the patches in the series).
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-01-17 16:03 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 ` [1/2] " Kalle Valo
[not found] ` <20180108173523.B23C360B22@smtp.codeaurora.org>
2018-01-08 17:44 ` 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 [this message]
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=9978263.24XfVAzbPX@bentobox \
--to=sven@narfation.org \
--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;
as well as URLs for NNTP newsgroup(s).