mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Wentao Liang <vulab@iscas.ac.cn>
Cc: Jeff Johnson <jeff.johnson@oss.qualcomm.com>,
	Jeff Johnson <jjohnson@kernel.org>,
	linux-wireless@vger.kernel.org, ath11k@lists.infradead.org,
	linux-kernel@vger.kernel.org, workflows@vger.kernel.org
Subject: Re: [PATCH RESEND] wifi: ath11k: release the rproc reference on teardown
Date: Wed, 11 Nov 2026 08:43:01 +0200	[thread overview]
Message-ID: <20261111064301.GC86558@killaraus.ideasonboard.com> (raw)
In-Reply-To: <179436839700.3055208.16759622808608708086@iscas.ac.cn>

On Wed, Nov 11, 2026 at 03:39:57AM -0000, Wentao Liang wrote:
> Hi Laurent,
> 
> My main goal is to study how to find bugs in the Linux kernel.

Why ?

> When
> that work finds a bug, I also want to help fix it and contribute to
> the kernel.
> 
> Static analysis flagged possible bugs, and we reviewed them by hand
> with help from DeepSeek and GPT-6.1 Sol. Even after that review, many
> of them still seemed worth looking into. I got excited about the
> findings and sent more patches than I could follow up on. I regretted
> that decision soon afterward. I should have sent fewer patches and
> replied sooner. I'm sorry for the extra work this caused.
> 
> I'll use this shared address only to reply to feedback I haven't yet
> answered on patches I've already sent. I'll go through that feedback
> one message at a time and respect the decisions maintainers have
> already made. If any of the remaining patches are still worth
> considering, I'd be grateful for the chance to answer questions
> about them.
> 
> I still hope to contribute to the kernel in the future. If I have
> the chance to do so, I'll use my own email address, respect the
> maintainers' requests, and send only as many patches as I can
> follow up on promptly.
> 
> Thanks,
> Wentao

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2026-11-11  6:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-03 10:29 Wentao Liang
2026-11-03 10:40 ` Krzysztof Kozlowski
2026-11-03 11:11 ` Krzysztof Kozlowski
2026-11-09 15:00 ` Jeff Johnson
2026-11-10 10:34   ` Wentao Liang
2026-11-10 12:27     ` Laurent Pinchart
2026-11-11  3:39       ` Wentao Liang
2026-11-11  6:43         ` Laurent Pinchart [this message]
2026-11-10 17:56     ` Jeff Johnson

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=20261111064301.GC86558@killaraus.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=ath11k@lists.infradead.org \
    --cc=jeff.johnson@oss.qualcomm.com \
    --cc=jjohnson@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=vulab@iscas.ac.cn \
    --cc=workflows@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

all inboxes | Powered by JetHome®