DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, konstantin.ananyev@huawei.com,
	vladimir.medvedkin@intel.com,  Aaron Conole <aconole@redhat.com>
Subject: Re: [PATCH] AGENTS.md: add additional checks for crypto related code
Date: Sun, 12 Jul 2026 17:49:38 +0200	[thread overview]
Message-ID: <_A8u46MgQQuCAo2fxGs2lg@monjalon.net> (raw)
In-Reply-To: <20260625230536.147975-1-stephen@networkplumber.org>

26/06/2026 01:05, Stephen Hemminger:
> Security related code is a high value target and extra precautions
> should be taken. These are hard to catch with checkpatch alone
> so add additional rules to AGENTS file.
> 
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>

Applied, thanks.




      reply	other threads:[~2026-07-12 15:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-25 23:05 [PATCH] AGENTS.md: add additional checks for crypto related code Stephen Hemminger
2026-07-12 15:49 ` Thomas Monjalon [this message]

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=_A8u46MgQQuCAo2fxGs2lg@monjalon.net \
    --to=thomas@monjalon.net \
    --cc=aconole@redhat.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@huawei.com \
    --cc=stephen@networkplumber.org \
    --cc=vladimir.medvedkin@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox