DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: fengchengwen <fengchengwen@huawei.com>
To: <datshan@qq.com>, <thomas@monjalon.net>, <stephen@networkplumber.org>
Cc: <aconole@redhat.com>, <dev@dpdk.org>
Subject: Re: [PATCH v3] devtools: support local opencode agent for patch review
Date: Tue, 4 Aug 2026 16:41:39 +0800	[thread overview]
Message-ID: <047b7271-725d-46b0-a6b7-6e59bbf39863@huawei.com> (raw)
In-Reply-To: <tencent_CFE5ECAF36405DFD2FB29DB7319B04E72C08@qq.com>

Ping for review

Thanks

On 7/25/2026 4:43 PM, datshan@qq.com wrote:
> From: Chengwen Feng <fengchengwen@huawei.com>
> 
> Currently review-patch.py only supports cloud AI providers
> (Anthropic, OpenAI, xAI, Google) via REST API, requiring API keys.
> 
> Add a --via option that invokes the locally installed opencode CLI as
> the review runner instead of making HTTP calls. opencode reads
> AGENTS.md from the DPDK project directory automatically, needing no
> configuration beyond opencode on PATH.
> 
> The --via and -p/--provider options are independent -- via routes to
> the local agent mode while -p continues to use the cloud API path.
> 
> Signed-off-by: Chengwen Feng <fengchengwen@huawei.com>

  reply	other threads:[~2026-08-04  8:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260703091902.525837-1-datshan@qq.com>
2026-07-06  6:29 ` [PATCH v2] devtools: support local opencode agent for patch review datshan
2026-07-25  8:43 ` [PATCH v3] " datshan
2026-08-04  8:41   ` fengchengwen [this message]
2026-08-04 12:22   ` Morten Brørup
2026-08-04 16:18   ` Stephen Hemminger
2026-08-05  6:12 ` [PATCH v4] " datshan
2026-08-07  3:11 ` [PATCH v5] " Chengwen Feng
2026-08-07  3:32   ` fengchengwen
2026-08-26  8:12   ` fengchengwen
2026-08-28 16:58   ` Stephen Hemminger

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=047b7271-725d-46b0-a6b7-6e59bbf39863@huawei.com \
    --to=fengchengwen@huawei.com \
    --cc=aconole@redhat.com \
    --cc=datshan@qq.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.org \
    --cc=thomas@monjalon.net \
    /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