From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Jakub Kicinski <kuba@kernel.org>,
Alexander Lobakin <aleksander.lobakin@intel.com>
Cc: <horms@kernel.org>, <edumazet@google.com>, <sdf@fomichev.me>,
<aleksandr.loktionov@intel.com>, <ast@kernel.org>,
<john.fastabend@gmail.com>, <bpf@vger.kernel.org>,
<netdev@vger.kernel.org>, <davem@davemloft.net>,
<andrew+netdev@lunn.ch>, <hawk@kernel.org>,
<nxne.cnse.osdt.itp.upstreaming@intel.com>,
<magnus.karlsson@intel.com>, <pabeni@redhat.com>,
<jacob.e.keller@intel.com>, <daniel@iogearbox.net>,
<maciej.fijalkowski@intel.com>
Subject: Re: [net-next,3/5] ice: migrate to netdev ops lock
Date: Tue, 17 Mar 2026 09:15:46 -0700 [thread overview]
Message-ID: <21a23b98-5014-4330-998f-53acfe705d67@intel.com> (raw)
In-Reply-To: <20260317085025.6459821c@kernel.org>
On 3/17/2026 8:50 AM, Jakub Kicinski wrote:
> On Tue, 17 Mar 2026 16:30:26 +0100 Alexander Lobakin wrote:
>> BTW, if it's not top secret, how do you run these AI reviews? Because
>> Tony used the same link as these reports provide to deploy a setup, but
>> we didn't manage to get as meaningful results as yours. That's why
>> several respins of this series only due to your AI reviews, sorry =\
>
> Nothing secret, I didn't push it to the main NIPA repo because it
> mostly vibecoded crap which is embarrassing. You can see it here:
>
> https://github.com/kuba-moo/nipa/tree/air
>
> It is just Chris's prompts + semcode. We run the prompts with
> sub-agents enabled (the "orc" prompt). Right now it runs on Claude,
> the subagents are supposed to pick the model by themselves depending
> on complexity.
>
> I don't think we do anything special, if anything it's probably the
> mode (orc mode thing) that makes a difference?
That's possible. I'm still pursing it but, at least so far, I haven't
found a way to get orc mode working with my tooling.
Thanks,
Tony
next prev parent reply other threads:[~2026-03-17 16:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 22:06 [PATCH net-next 0/5][pull request] ice: add support for devmem/io_uring Rx and Tx Tony Nguyen
2026-03-10 22:06 ` [PATCH net-next 1/5] libeth: pass Rx queue index to PP when creating a fill queue Tony Nguyen
2026-03-10 22:06 ` [PATCH net-next 2/5] libeth: handle creating pools with unreadable buffers Tony Nguyen
2026-03-10 22:06 ` [PATCH net-next 3/5] ice: migrate to netdev ops lock Tony Nguyen
2026-03-13 1:46 ` [net-next,3/5] " Jakub Kicinski
2026-03-16 15:10 ` Alexander Lobakin
2026-03-16 23:16 ` Jakub Kicinski
2026-03-17 15:30 ` Alexander Lobakin
2026-03-17 15:50 ` Jakub Kicinski
2026-03-17 16:15 ` Tony Nguyen [this message]
2026-03-17 17:29 ` Jakub Kicinski
2026-03-17 17:57 ` Tony Nguyen
2026-03-10 22:06 ` [PATCH net-next 4/5] ice: implement Rx queue management ops Tony Nguyen
2026-03-10 22:06 ` [PATCH net-next 5/5] ice: add support for transmitting unreadable frags Tony Nguyen
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=21a23b98-5014-4330-998f-53acfe705d67@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=aleksander.lobakin@intel.com \
--cc=aleksandr.loktionov@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=nxne.cnse.osdt.itp.upstreaming@intel.com \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
/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.