All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Howard <kernel@nhoward.dev>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Yingjie Cao <yingjcao@sigvoid.com>,
	linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] wifi: mac80211: only accept IBSS channel switch from our own BSSID
Date: Mon, 6 Jul 2026 23:20:26 -0400	[thread overview]
Message-ID: <akxwel29T0_gvu8Z@gpu1> (raw)
In-Reply-To: <b7dab24792025a5a95b719ef7d508fb109859ec1.camel@sipsolutions.net>

On Mon, Jul 06, 2026 at 10:53:33AM +0200, Johannes Berg wrote:
> On Tue, 2026-06-23 at 15:31 -0400, Nathan Howard wrote:
> > 
> > So, what's the litmus test?
> 
> I don't know, tbh.
> 
> > I've been watching this list for some time
> > now.  I've seen (what appears) to be an ushering of distrust brought
> > on by llm's.  This also seems to have come into prominence within the last 6 or
> > so months.  I understand the cautious approach, but what if one's been
> > working diligently (and quietly), and has spent many hours studying and
> > preparing a driver series (for oneself and submission to the kernel)?
> > I've always done well by doing my homework the hard way.  But now,
> > submissions are met with skepticism... that the work must have been
> > assisted-by if the person doesn't have a track record.  How should one defend
> > his work (I'd rather not share credit with a machine when my work is my own)?
> > To be clear, my question is sourcing from what I've seen to be trending
> > more recently whereby several submissions have been ?softly? tagged as assisted-by.
> > Maybe they were, but my point still stands.  Kindly provide guidance.
> 
> I'm convinced that if you've actually done the legwork you could defend
> the work you've done. If you're willing to go on the record saying you
> _didn't_ use an LLM I'm even going to believe it.

This sounds reasonable.

> 
> But if someone's sending "critical security fix that needs security@
> involvement" across a wide spectrum of places then yes, I'm going to be
> highly sceptical they actually know what they're doing on any individual
> one of the issues.
> 
> Like here. OK, this one didn't go to security@, and it's not even a
> wrong fix, but doing "Cc stable", Cc'ing half the world and not
> following up *at all* are all bad signs.

As does this.  Thank you for the guidance.


  reply	other threads:[~2026-07-07  3:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-23  9:04 [PATCH] wifi: mac80211: only accept IBSS channel switch from our own BSSID Yingjie Cao
2026-06-23  9:10 ` Johannes Berg
2026-06-23  9:12   ` Johannes Berg
2026-06-23 19:31     ` Nathan Howard
2026-07-06  8:53       ` Johannes Berg
2026-07-07  3:20         ` Nathan Howard [this message]
2026-07-07 13:43         ` Yingjie Cao

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=akxwel29T0_gvu8Z@gpu1 \
    --to=kernel@nhoward.dev \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=yingjcao@sigvoid.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 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.