Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Nicolas Escande" <nico.escande@gmail.com>
To: "Nicolas Escande" <nico.escande@gmail.com>,
	"Fernando Tapia" <fernan.tapia@fernandotapia.eu>,
	<ath11k@lists.infradead.org>
Cc: <jjohnson@kernel.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH ath-next] wifi: ath11k: don't create a duplicate peer on the same pdev
Date: Tue, 17 Nov 2026 10:04:46 +0100	[thread overview]
Message-ID: <DMXD6CV42W7U.2MVL2J7R8J7W1@gmail.com> (raw)
In-Reply-To: <DMXCW8192G9S.19BCMYODX8KSK@gmail.com>

On Tue Nov 17, 2026 at 9:51 AM CET, Nicolas Escande wrote:
>
> Guys, I'm all for fixing bugs, but at some point you need to start reading
> and searching the mailing list before pointing your LLM to any crashing
> target. This is the third time someone posted a fix for this issue:
>
> https://lore.kernel.org/linux-wireless/1316ed692b84f1d956e4854d9e974569a3961795.1784792420.git.repk@triplefau.lt/
> https://lore.kernel.org/linux-wireless/20261001164139.370144-1-patricktlawler@gmail.com/

Even worse, 4 patches in total:
https://lore.kernel.org/linux-wireless/1316ed692b84f1d956e4854d9e974569a3961795.1784792420.git.repk@triplefau.lt/
https://lore.kernel.org/linux-wireless/20261001164139.370144-1-patricktlawler@gmail.com/
https://lore.kernel.org/linux-wireless/20261026040302.2635133-1-dencity7@gmail.com/
https://lore.kernel.org/linux-wireless/20261113120325.2913-1-fernan.tapia@fernandotapia.eu/

  reply	other threads:[~2026-11-17  9:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-13 12:03 [PATCH ath-next] wifi: ath11k: don't create a duplicate peer on the same pdev Fernando Tapia
2026-11-17  8:51 ` Nicolas Escande
2026-11-17  9:04   ` Nicolas Escande [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-11-16 18:11 Ure, Christopher R.

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=DMXD6CV42W7U.2MVL2J7R8J7W1@gmail.com \
    --to=nico.escande@gmail.com \
    --cc=ath11k@lists.infradead.org \
    --cc=fernan.tapia@fernandotapia.eu \
    --cc=jjohnson@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox