DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Anoob Joseph <anoobj@marvell.com>,
	Akhil Goyal <gakhil@marvell.com>,
	David Marchand <david.marchand@redhat.com>,
	Ali Alnubani <alialnu@nvidia.com>
Cc: dev@dpdk.org, Aakash Sasidharan <asasidharan@marvell.com>,
	bruce.richardson@intel.com, rjarry@redhat.com
Subject: Re: [PATCH] test/crypto: fix non ASCII character
Date: Tue, 05 Mar 2024 14:25:28 +0100	[thread overview]
Message-ID: <3997823.ZaRXLXkqSa@thomas> (raw)
In-Reply-To: <DM4PR12MB5167371538449611288E5134DA222@DM4PR12MB5167.namprd12.prod.outlook.com>

05/03/2024 13:14, Ali Alnubani:
> > Subject: [PATCH] test/crypto: fix non ASCII character
> > 
> > Fix non ASCII character in the comment. Revert to original text.
> > 
> > Bugzilla ID: 1396
> > Fixes: f97c63f4f445 ("test/crypto: add AES-GCM external mbuf case")
> > 
> > Signed-off-by: Anoob Joseph <anoobj@marvell.com>
> > ---
> 
> Build passes with this patch, thanks!
> 
> Tested-by: Ali Alnubani <alialnu@nvidia.com>

Reported-by: Ali Alnubani <alialnu@nvidia.com>

Applied, thanks.


The script buildtools/get-test-suites.py is not tolerant with Unicode.
We may be more flexible probably.
Bruce, Robin, what do you think about allowing Unicode characters in this script?



  reply	other threads:[~2024-03-05 13:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-05 11:34 Anoob Joseph
2024-03-05 12:14 ` Ali Alnubani
2024-03-05 13:25   ` Thomas Monjalon [this message]
2024-03-05 13:27     ` David Marchand
2024-03-05 13:29       ` Robin Jarry

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=3997823.ZaRXLXkqSa@thomas \
    --to=thomas@monjalon.net \
    --cc=alialnu@nvidia.com \
    --cc=anoobj@marvell.com \
    --cc=asasidharan@marvell.com \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=rjarry@redhat.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).