All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: "Wu. JackBB (GSM)" <JackBB_Wu@compal.com>
Cc: Loic Poulain <loic.poulain@oss.qualcomm.com>,
	Sergey Ryazanov <ryazanov.s.a@gmail.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	"Andrew Lunn" <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	"Eric Dumazet" <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>,
	Wen-Zhi Huang <wen-zhi.huang@mediatek.com>,
	Shi-Wei Yeh <shi-wei.yeh@mediatek.com>,
	"Minano Tseng" <Minano.tseng@mediatek.com>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	"Simon Horman" <horms@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	"Yu. Robert (GSM)" <robert_yu@compal.com>,
	"Chang. Jeff (GSM)" <Jeff_Chang@compal.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: [External Mail] Re: [PATCH v8 1/6] net: wwan: t9xx: Add PCIe core
Date: Mon, 21 Sep 2026 13:23:23 -0700	[thread overview]
Message-ID: <20260921132323.7e6f76d3@kernel.org> (raw)
In-Reply-To: <690e3d6d04ba47efba2b4cda7b18e42e@compal.com>

On Mon, 21 Sep 2026 07:06:23 +0000 Wu. JackBB (GSM) wrote:
> Two questions on the prompts document.
> 
> Are the following hard requirements the series has to meet, or targets
> for the tool?

Targets for the LLM but also these are describing a high quality
submission in general.

>  - line 44: "Ideal patches are between 200 and 700 LoC (added +
>    removed, not counting context)."
>  - line 46: "Avoid series larger than 2.5k LoC. The first series is
>    usually larger, but must not exceed 4k LoC."
>  - lines 57-58: "Series 1 should aim to add the simplest possible
>    version of the driver which nonetheless can send and receive a
>    trivial (no offloads) packet."
>  - line 117: "Avoid the use of managed APIs (``devm_``, ``pcim_``)."
> 
> On the packet one: this series carries no netdev because an earlier
> review found the driver too large to submit at once, so the network
> functionality was split into follow-up series.

That's fine.

> The document also asks for no defensive checks (lines 119-120) and few
> code comments (line 124).  That runs against the direction of the AI review
> we have been getting, where both have been growing.  Is the current
> direction still fine?

The kernel coding guide has not changed, defensive checks are still
discouraged. If AI is suggesting checks that can't trigger just comment
on the review or add a comment / WARN to the code to mark the condition
as impossible.


  reply	other threads:[~2026-09-21 20:23 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-14 10:31 [PATCH v8 0/6] net: wwan: t9xx: Add MediaTek T9XX WWAN driver Jack Wu via B4 Relay
2026-09-14 10:31 ` Jack Wu
2026-09-14 10:31 ` [PATCH v8 1/6] net: wwan: t9xx: Add PCIe core Jack Wu via B4 Relay
2026-09-14 10:31   ` Jack Wu
2026-09-19 23:54   ` Jakub Kicinski
2026-09-21  7:06     ` [External Mail] " Wu. JackBB (GSM)
2026-09-21 20:23       ` Jakub Kicinski [this message]
2026-09-19 23:54   ` Jakub Kicinski
2026-09-21 10:16     ` [External Mail] " Wu. JackBB (GSM)
2026-09-14 10:31 ` [PATCH v8 2/6] net: wwan: t9xx: Add control plane transaction layer Jack Wu via B4 Relay
2026-09-14 10:31   ` Jack Wu
2026-09-14 10:31 ` [PATCH v8 3/6] net: wwan: t9xx: Add control DMA interface Jack Wu via B4 Relay
2026-09-14 10:31   ` Jack Wu
2026-09-14 10:31 ` [PATCH v8 4/6] net: wwan: t9xx: Add control port Jack Wu via B4 Relay
2026-09-14 10:31   ` Jack Wu
2026-09-19 23:54   ` Jakub Kicinski
2026-09-22  6:28     ` Wu. JackBB (GSM)
2026-09-14 10:31 ` [PATCH v8 5/6] net: wwan: t9xx: Add FSM thread Jack Wu via B4 Relay
2026-09-14 10:31   ` Jack Wu
2026-09-19 23:54   ` Jakub Kicinski
2026-09-22  6:44     ` Wu. JackBB (GSM)
2026-09-14 10:31 ` [PATCH v8 6/6] net: wwan: t9xx: Add AT & MBIM WWAN ports Jack Wu via B4 Relay
2026-09-14 10:31   ` Jack Wu
2026-09-19 23:54   ` Jakub Kicinski
2026-09-22  7:06     ` Wu. JackBB (GSM)

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=20260921132323.7e6f76d3@kernel.org \
    --to=kuba@kernel.org \
    --cc=JackBB_Wu@compal.com \
    --cc=Jeff_Chang@compal.com \
    --cc=Minano.tseng@mediatek.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=loic.poulain@oss.qualcomm.com \
    --cc=matthias.bgg@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=robert_yu@compal.com \
    --cc=ryazanov.s.a@gmail.com \
    --cc=shi-wei.yeh@mediatek.com \
    --cc=skhan@linuxfoundation.org \
    --cc=wen-zhi.huang@mediatek.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.