DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Tomasz Duszynski <tduszynski@marvell.com>
Cc: dev@dpdk.org, jerinj@marvell.com
Subject: Re: [dpdk-dev] [PATCH] devtools: relax headline prefix check
Date: Fri, 06 Aug 2021 17:08:26 +0200	[thread overview]
Message-ID: <5776256.FH8VHCdSZe@thomas> (raw)
In-Reply-To: <20210727131917.120743-1-tduszynski@marvell.com>

27/07/2021 15:19, Tomasz Duszynski:
> In order to avoid code duplication common code shared across drivers
> is stored under drivers/common.
> 
> Currently if one needs to introduce changes to common and particular
> driver i.e common/driver and net/driver separate patches needs to be
> prepared otherwise warning about wrong headline prefix gets printed.

No please don't split patches just to make a script happy :)
We can tolerate few warnings if not meaningful.
But I agree it would be better to avoid such wrong warning.

> In order to avoid that script should allow cases where changes to
> drivers/common/driver and drivers/group/driver belong to the same patch.
> 
> Signed-off-by: Tomasz Duszynski <tduszynski@marvell.com>
[...]
> --- a/devtools/check-git-log.sh
> +++ b/devtools/check-git-log.sh
> @@ -80,6 +80,10 @@ bad=$(for commit in $commits ; do
>  	drv=$(echo "$files" | grep '^drivers/' | cut -d "/" -f 2,3 | sort -u)
>  	drvgrp=$(echo "$drv" | cut -d "/" -f 1 | uniq)
>  	if [ $(echo "$drvgrp" | wc -l) -gt 1 ] ; then
> +		if [ $(echo "$drvgrp" | grep -c "common") -eq 1 ] &&
> +		   [ $(echo "$drvgrp" | grep -cv "common") -eq 1 ] ; then
> +			continue

It means you allow one common subdir and exactly one non-common subdir.
I think it is too much restrictive because it makes sense
to change a shared code and several related drivers.

Thanks for working on such improvement.



      reply	other threads:[~2021-08-06 15:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-27 13:19 Tomasz Duszynski
2021-08-06 15:08 ` 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=5776256.FH8VHCdSZe@thomas \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=tduszynski@marvell.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;
as well as URLs for NNTP newsgroup(s).