From: Michael Mera <dev@michaelmera.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: Marcin Rokicki <marcin.rokicki@gmail.com>,
"linux-wireless\@vger.kernel.org"
<linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] ath10k: fix out of bounds access to local buffer
Date: Mon, 22 May 2017 14:01:15 +0900 [thread overview]
Message-ID: <87wp99eb8k.fsf@michaelmera.com> (raw)
In-Reply-To: <87d1b9v044.fsf@qca.qualcomm.com>
Kalle Valo <kvalo@qca.qualcomm.com> writes:
> I added a link to the corresponding ath10k page. BTW, it's a wiki so
> everyone are free to improve the instructions on their own.
As it was my first contribution, I didn't feel like editing things
without some sort of approval first. I will try to be more audacious
next time.
Thank you very much,
Michael Mera
prev parent reply other threads:[~2017-05-22 5:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 5:39 [PATCH] ath10k: fix out of bounds access to local buffer Michael Mera
2017-04-24 6:56 ` Marcin Rokicki
2017-04-24 7:41 ` Michael Mera
2017-04-24 7:46 ` Marcin Rokicki
2017-05-16 5:31 ` Kalle Valo
2017-05-22 5:01 ` Michael Mera [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=87wp99eb8k.fsf@michaelmera.com \
--to=dev@michaelmera.com \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=marcin.rokicki@gmail.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).