From: Bandhan Pramanik <bandhanpramanik06.foss@gmail.com>
To: Bjorn Helgaas <helgaas@kernel.org>, Jeff Johnson <jjohnson@kernel.org>
Cc: linux-wireless@vger.kernel.org, linux-pci@vger.kernel.org,
ath10k@lists.infradead.org,
Manivannan Sadhasivam <mani@kernel.org>
Subject: Re: Packet loss with QCA9377 (ath10k) on ASUS VivoBook E410KA
Date: Thu, 07 Aug 2025 11:33:08 +0530 [thread overview]
Message-ID: <BBAB0136-BB7C-4D59-B29D-2F35FC29D7AC@gmail.com> (raw)
In-Reply-To: <20250806204018.GA14933@bhelgaas>
I'll tell the guy to clone the ath-next branch then and will inform you pretty soon.
Bandhan
next prev parent reply other threads:[~2025-08-07 6:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-31 18:39 Packet loss with QCA9377 (ath10k) on ASUS VivoBook E410KA Bandhan Pramanik
2025-08-06 20:40 ` Bjorn Helgaas
2025-08-07 6:03 ` Bandhan Pramanik [this message]
2025-08-07 8:23 ` Manivannan Sadhasivam
2025-08-07 22:04 ` Bandhan Pramanik
2025-08-27 17:28 ` Bandhan Pramanik
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=BBAB0136-BB7C-4D59-B29D-2F35FC29D7AC@gmail.com \
--to=bandhanpramanik06.foss@gmail.com \
--cc=ath10k@lists.infradead.org \
--cc=helgaas@kernel.org \
--cc=jjohnson@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mani@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