Netdev List
 help / color / mirror / Atom feed
From: Stefan Agner <stefan@agner.ch>
To: Jakub Raczynski <j.raczynski@samsung.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>,
	Maxime Chevallier <maxime.chevallier@bootlin.com>,
	Ovidiu Panait <ovidiu.panait.rb@renesas.com>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	Alexandre Torgue <alexandre.torgue@foss.st.com>,
	netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com,
	linux-arm-kernel@lists.infradead.org,
	regressions@lists.linux.dev
Subject: Re: [PATCH net v2] net: stmmac: resume PHY before hardware setup when opening the interface
Date: Fri, 31 Jul 2026 12:18:08 +0200	[thread overview]
Message-ID: <9f7506a99b22293bae3f467f64506627@agner.ch> (raw)
In-Reply-To: <ak1rseUKTWFKzBib@AMDC4622.eu.corp.samsungelectronics.net>

Hi Jakub,

On 2026-07-07 23:13, Jakub Raczynski wrote:
> Please read
> https://www.kernel.org/doc/html/latest/process/maintainer-netdev.html
> in this case 'don’t repost your patches within one 24h period'
> 
> Because:
> - you have two patches now processing and no changes requested yet,
>   nor did you get AI review that is currently employed
>   https://patchwork.kernel.org/project/netdevbpf/patch/20260707195425.405989-1-stefan@agner.ch/
>   and
>   https://patchwork.kernel.org/project/netdevbpf/patch/20260707162146.73823-1-stefan@agner.ch/

Isn't the definition of "repost" the same patch?

I took Andrew Lunn's comment as a change request, hence v2...

> - This change is actually broken - in previous patch rtnl_lock() was asserted
>   by dev_ioctl(), but in this version it is not asserted anywhere and will
>   trigger WARN_ONCE().
> - Full tests within an hour is possible, but no need to rush patches
> - Please spend time reviewing patches, as I spent few minutes to make sure
>   you (or rather Fable AI) is correct that rtnl_lock() was asserted, so my
>   review would be accurate (previous patch was ok, this is not).
> - Please respond yourself to comments, take time to understand codebase.
>   I would prefer not getting copy-paste answer from AI,
>   we have Sashiko review for that.

I am guessing you allude to my response at
https://patchwork.kernel.org/project/netdevbpf/patch/20260707162146.73823-1-stefan@agner.ch/#27051411

Can I influence the prompt for Sashiko? From my point of view the
response was for a specific architectural questions, which needed a
specific prompt to get the answer for. I've clearly declared that I've
used AI to aid for this discussion, is that no allowed?

> - Missing link to previous thread, shown below
> - Moving code to other lines does not justify dropping "Assisted by AI"

Whoops, yeah those two are failure on my part. Sorry about that.

Thanks for your help guiding me through the process! I intend to send
out v3, which at this point looks to be pretty much v2 plus formal fixes
and adding a tested by tag.

--
Stefan

  parent reply	other threads:[~2026-07-31 10:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <message-id-of-your-v1-mail>
2026-07-07 19:54 ` [PATCH net v2] net: stmmac: resume PHY before hardware setup when opening the interface Stefan Agner
2026-07-07 21:13   ` Jakub Raczynski
2026-07-07 21:45     ` Jakub Raczynski
2026-07-31 10:18     ` Stefan Agner [this message]
2026-07-08  8:00   ` Alexander Stein
2026-07-08  9:16   ` Maxime Chevallier
2026-07-21  8:12     ` Paolo Abeni
2026-07-31 10:03       ` Stefan Agner
2026-07-31 10:12         ` Maxime Chevallier
2026-07-22 14:42   ` Jakub Kicinski

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=9f7506a99b22293bae3f467f64506627@agner.ch \
    --to=stefan@agner.ch \
    --cc=alexandre.torgue@foss.st.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=j.raczynski@samsung.com \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=maxime.chevallier@bootlin.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=ovidiu.panait.rb@renesas.com \
    --cc=pabeni@redhat.com \
    --cc=regressions@lists.linux.dev \
    --cc=rmk+kernel@armlinux.org.uk \
    /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