DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Iremonger, Bernard" <bernard.iremonger@intel.com>
To: Chuanshe Zhang <zhangchuanshe@icloudshield.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH] examples/flow_classify: fix spelling when log error
Date: Wed, 23 Feb 2022 16:05:38 +0000	[thread overview]
Message-ID: <DM6PR11MB28900BBDFE0C59D28B14413CEF3C9@DM6PR11MB2890.namprd11.prod.outlook.com> (raw)
In-Reply-To: <1642474174-3963-1-git-send-email-zhangchuanshe@icloudshield.com>

Hi Chuanshe,

> -----Original Message-----
> From: Chuanshe Zhang <zhangchuanshe@icloudshield.com>
> Sent: Tuesday, January 18, 2022 2:50 AM
> To: dev@dpdk.org
> Cc: Iremonger, Bernard <bernard.iremonger@intel.com>
> Subject: [PATCH] examples/flow_classify: fix spelling when log error
> 
> Signed-off-by: Chuanshe Zhang <zhangchuanshe@icloudshield.com>
> ---
>  examples/flow_classify/flow_classify.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/examples/flow_classify/flow_classify.c
> b/examples/flow_classify/flow_classify.c
> index 6185b34..97708b7 100644
> --- a/examples/flow_classify/flow_classify.c
> +++ b/examples/flow_classify/flow_classify.c
> @@ -430,7 +430,7 @@ struct rte_flow_query_count count = {
>  			&ntuple_filter->dst_ip,
>  			&ntuple_filter->dst_ip_mask);
>  	if (ret != 0) {
> -		flow_classify_log("failed to read source address/mask:
> %s\n",
> +		flow_classify_log("failed to read destination address/mask:
> %s\n",
>  			in[CB_FLD_DST_ADDR]);
>  		return ret;
>  	}
> --
> 1.8.3.1

 
/dpdk_22_03/devtools# ./checkpatches.sh examples-flow_classify-fix-spelling-when-log-error.patch

### [PATCH] examples/flow_classify: fix spelling when log error
WARNING:COMMIT_MESSAGE: Missing commit description - Add an appropriate one

/dpdk_22_03/devtools# ./check-git-log.sh -1
Missing 'Fixes' tag:
        examples/flow_classify: fix spelling when log error


Otherwise, the fix looks good.

Regards,

Bernard.


  reply	other threads:[~2022-02-23 16:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-18  2:49 Chuanshe Zhang
2022-02-23 16:05 ` Iremonger, Bernard [this message]
2022-03-08 11:43   ` Thomas Monjalon
2022-03-08 12:00     ` Iremonger, Bernard

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=DM6PR11MB28900BBDFE0C59D28B14413CEF3C9@DM6PR11MB2890.namprd11.prod.outlook.com \
    --to=bernard.iremonger@intel.com \
    --cc=dev@dpdk.org \
    --cc=zhangchuanshe@icloudshield.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).