From: Stephen Hemminger <stephen@networkplumber.org>
To: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH] devtools: allow patch to multiple groups for the same driver
Date: Mon, 14 Sep 2026 10:08:34 -0700 [thread overview]
Message-ID: <20260914100834.25389d03@phoenix.local> (raw)
In-Reply-To: <20230420121240.28035-1-viacheslavo@nvidia.com>
On Thu, 20 Apr 2023 15:12:40 +0300
Viacheslav Ovsiienko <viacheslavo@nvidia.com> wrote:
> The PMD's source code resides in the ./drivers folder of the
> DPDK project and split into the several groups depending on the
> PMD class (common, net, regex, etc.).
>
> For some vendors the drivers of different classes operate over
> the same hardware, for example Nvidia PMDs operate over ConnectX
> NIC series. It often happens the same minor fixes should be applied
> to the multiple drivers of the same vendor in the different classes.
>
> The check-git-log.sh script checks the consistence of patch
> affected files and patch commit message headline and prevents
> updating multiple drivers in single commit.
>
> This patch mitigates this strict check and allows to update
> multiple drivers in different classes for the single vendor.
>
> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
> ---
This patch has sat for years now with no response.
As a maintainer, using check-git-log is just advice and it doesn't need to be exact.
So marking this as Rejected due to lack of ack's
prev parent reply other threads:[~2026-09-14 17:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 12:12 [PATCH] devtools: allow patch to multiple groups for the same driver Viacheslav Ovsiienko
2026-09-14 17:08 ` Stephen Hemminger [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=20260914100834.25389d03@phoenix.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=viacheslavo@nvidia.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.