From: Johannes Berg <johannes@sipsolutions.net>
To: Arnav Kapoor <kapoorarnav43@gmail.com>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
syzbot+15f88dfa580000@syzkaller.appspotmail.com,
Arnav Rawat <arnavrawat2000@gmail.com>
Subject: Re: [PATCH] mac80211: Fix and improve debugfs TSF access protection
Date: Tue, 20 Jan 2026 08:54:54 +0100 [thread overview]
Message-ID: <eece33b4580bb35d28be8ffba7957bde509f59cf.camel@sipsolutions.net> (raw)
In-Reply-To: <20260119194057.53339-1-kapoorarnav43@gmail.com> (sfid-20260119_204306_054164_7A51E36C)
On Tue, 2026-01-20 at 01:10 +0530, Arnav Kapoor wrote:
> This patch comprehensively addresses reviewer feedback on the debugfs TSF
> access protection:
Please go away until you understood how that contributing to the kernel
isn't dumping reviewer feedback into an LLM.
johannes
next parent reply other threads:[~2026-01-20 7:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260119194057.53339-1-kapoorarnav43@gmail.com>
2026-01-20 7:54 ` Johannes Berg [this message]
2026-01-20 7:54 ` [PATCH] mac80211: Fix and improve debugfs TSF access protection syzbot
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=eece33b4580bb35d28be8ffba7957bde509f59cf.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arnavrawat2000@gmail.com \
--cc=kapoorarnav43@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=syzbot+15f88dfa580000@syzkaller.appspotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox