From: "Iremonger, Bernard" <bernard.iremonger@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
Chuanshe Zhang <zhangchuanshe@icloudshield.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH] examples/flow_classify: fix spelling when log error
Date: Tue, 8 Mar 2022 12:00:04 +0000 [thread overview]
Message-ID: <DM6PR11MB2890E0EDD3A8FADB17DFE3C7EF099@DM6PR11MB2890.namprd11.prod.outlook.com> (raw)
In-Reply-To: <3988050.1xdlsreqCQ@thomas>
Hi Thomas,
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Tuesday, March 8, 2022 11:44 AM
> To: Chuanshe Zhang <zhangchuanshe@icloudshield.com>
> Cc: dev@dpdk.org; Iremonger, Bernard <bernard.iremonger@intel.com>
> Subject: Re: [PATCH] examples/flow_classify: fix spelling when log error
>
> 23/02/2022 17:05, Iremonger, Bernard:
> > Hi Chuanshe,
> >
> > From: Chuanshe Zhang <zhangchuanshe@icloudshield.com>
> > >
> > > Signed-off-by: Chuanshe Zhang <zhangchuanshe@icloudshield.com>
> > > ---
> > > - flow_classify_log("failed to read source address/mask:
> > > %s\n",
> > > + flow_classify_log("failed to read destination address/mask:
> > > %s\n",
> >
> > ### [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.
>
> Applied, thanks.
>
You can add my ack to this patch
prev parent reply other threads:[~2022-03-08 12:00 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
2022-03-08 11:43 ` Thomas Monjalon
2022-03-08 12:00 ` Iremonger, Bernard [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=DM6PR11MB2890E0EDD3A8FADB17DFE3C7EF099@DM6PR11MB2890.namprd11.prod.outlook.com \
--to=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
--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).