linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: "Viktor Jägersküpper" <viktor_jaegerskuepper@freenet.de>
Cc: Mark O'Donovan <shiftee@posteo.net>,
	linux-wireless@vger.kernel.org, hqjagain@gmail.com,
	ath9k-devel@qca.qualcomm.com, davem@davemloft.net,
	kuba@kernel.org, Roman Mamedov <rm@romanrm.net>
Subject: Re: [PATCH 1/1] ath9k: Fix regression with Atheros 9271
Date: Thu, 16 Jul 2020 12:10:04 +0300	[thread overview]
Message-ID: <87y2nj7rmb.fsf@codeaurora.org> (raw)
In-Reply-To: <184f6897-40f8-949c-eca5-2bdb0d2aa8fb@freenet.de> ("Viktor \=\?utf-8\?Q\?J\=C3\=A4gersk\=C3\=BCpper\=22's\?\= message of "Thu, 16 Jul 2020 10:01:29 +0200")

Viktor Jägersküpper <viktor_jaegerskuepper@freenet.de> writes:

> [I fixed my e-mail address and CC'ed Roman]
>
> Mark O'Donovan:
>> This fix allows ath9k_htc modules to connect to WLAN once again.
>> 
>> Fixes: 2bbcaaee1fcb (ath9k: Fix general protection fault in
>> ath9k_hif_usb_rx_cb )
>> 
>> https://bugzilla.kernel.org/show_bug.cgi?id=208251
>> 
>> Signed-off-by: Mark O'Donovan <shiftee@posteo.net>
>
> This fixes the issue for me. Please don't forget:
> Reported-by: Roman Mamedov <rm@romanrm.net>
>
> And if you want to add this:
> Tested-by: Viktor Jägersküpper <viktor_jaegerskuepper@freenet.de>
>
> These additional lines are mainly useful if the patch doesn't work for someone
> else and they decide to report it, so hopefully Roman and I would receive the
> report, too. And we already have three threads for this bug.

Thanks, I will. Or well, actually patchwork automatically does that :)

-- 
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

  reply	other threads:[~2020-07-16  9:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-11  4:33 [PATCH 1/1] ath9k: Fix regression with Atheros 9271 Mark O'Donovan
2020-07-15 15:17 ` Kalle Valo
2020-07-16  8:01 ` Viktor Jägersküpper
2020-07-16  9:10   ` Kalle Valo [this message]
2020-07-20 16:37 ` 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=87y2nj7rmb.fsf@codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=ath9k-devel@qca.qualcomm.com \
    --cc=davem@davemloft.net \
    --cc=hqjagain@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rm@romanrm.net \
    --cc=shiftee@posteo.net \
    --cc=viktor_jaegerskuepper@freenet.de \
    /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).