From: Christoph Hellwig <hch@lst.de>
To: Kalle Valo <kvalo@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>,
ath11k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: ath11k vs ar_qrtr?
Date: Wed, 30 Nov 2022 14:22:44 +0100 [thread overview]
Message-ID: <20221130132244.GB3055@lst.de> (raw)
In-Reply-To: <87k03c4mdb.fsf@kernel.org>
On Wed, Nov 30, 2022 at 03:12:32PM +0200, Kalle Valo wrote:
> Heh, I'm learning something new here. But I wonder why nobody else has
> seen this?
Good question. How common is the ath11k hardware, especially on latptop
where it is required for installation given that only installers tend
to split up driver is non-standard ways.
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Kalle Valo <kvalo@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>,
ath11k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: ath11k vs ar_qrtr?
Date: Wed, 30 Nov 2022 14:22:44 +0100 [thread overview]
Message-ID: <20221130132244.GB3055@lst.de> (raw)
In-Reply-To: <87k03c4mdb.fsf@kernel.org>
On Wed, Nov 30, 2022 at 03:12:32PM +0200, Kalle Valo wrote:
> Heh, I'm learning something new here. But I wonder why nobody else has
> seen this?
Good question. How common is the ath11k hardware, especially on latptop
where it is required for installation given that only installers tend
to split up driver is non-standard ways.
next prev parent reply other threads:[~2022-11-30 13:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 12:28 ath11k vs ar_qrtr? Christoph Hellwig
2022-11-30 12:42 ` Kalle Valo
2022-11-30 12:52 ` Christoph Hellwig
2022-11-30 13:12 ` Kalle Valo
2022-11-30 13:12 ` Kalle Valo
2022-11-30 13:22 ` Christoph Hellwig [this message]
2022-11-30 13:22 ` Christoph Hellwig
2022-11-30 17:18 ` Kalle Valo
2022-11-30 17:18 ` Kalle Valo
2022-11-30 13:30 ` failed to insert STA entry for the AP (error -2) Christoph Hellwig
2022-11-30 13:30 ` Christoph Hellwig
2022-12-02 18:46 ` Kalle Valo
2022-12-02 18:46 ` Kalle Valo
2022-12-03 15:52 ` Christoph Hellwig
2022-12-03 15:52 ` Christoph Hellwig
2022-12-07 12:49 ` Kalle Valo
2022-12-07 12:49 ` Kalle Valo
2022-12-07 13:40 ` Christoph Hellwig
2022-12-07 13:40 ` Christoph Hellwig
2022-12-07 14:24 ` Cyril Brulebois
2022-12-07 14:24 ` Cyril Brulebois
2022-12-08 18:44 ` Kalle Valo
2022-12-08 18:44 ` 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=20221130132244.GB3055@lst.de \
--to=hch@lst.de \
--cc=ath11k@lists.infradead.org \
--cc=kvalo@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.