DPDK CI discussions
 help / color / mirror / Atom feed
From: Aditya Ambadipudi <Aditya.Ambadipudi@arm.com>
To: "ci@dpdk.org" <ci@dpdk.org>
Cc: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
	Dhruv Tripathi <Dhruv.Tripathi@arm.com>,
	Wathsala Wathawana Vithanage <wathsala.vithanage@arm.com>
Subject: How to remove a word from the dictionary.txt we are using in the CI/CD pipeline.
Date: Mon, 15 Apr 2024 20:41:29 +0000	[thread overview]
Message-ID: <PAVPR08MB91853B3126B08A68692A2872EF092@PAVPR08MB9185.eurprd08.prod.outlook.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1609 bytes --]

Hello folks,

My name is Aditya Ambadipudi. I work as a software engineer at Arm.

Recently we submitted a patch set for DPDK:
http://patches.dpdk.org/project/dpdk/patch/20240401013729.1466298-3-aditya.ambadipudi@arm.com/

And the CI/CD is failing for this patch because of the word Deque.
1787:adaquate->adequate
1788:adaquately->adequately
1789:adaquetely->adequately
1790:adaquit->adequate
1791:adaquitly->adequately
1975:adecuate->adequate
1977:adequat->adequate
1978:adequatly->adequately
1979:adequit->adequate
1980:adequite->adequate
1981:adequitely->adequately
1982:adequitly->adequately
18484:dequed->dequeued
18485:dequeing->dequeuing
18486:deques->dequeues
30005:inadiquate->inadequate
30006:inadquate->inadequate
61309:deque->dequeue


Code spell wants us to substitute all the places where we used the word "deque" with "dequeue".

We were wondering if it is possible to remove this rule from that dictionary that the CI/CD pipeline uses.  Or if there is a way to circumvent that rule.

The CR we created was specifically to add a Deque library to DPDK. The data structure we have created is a Deque and there is no other word that we can think of that describes that data structure better than "Deque".

Thank you,
Aditya Ambadipudi

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

[-- Attachment #2: Type: text/html, Size: 8276 bytes --]

             reply	other threads:[~2024-04-15 20:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-15 20:41 Aditya Ambadipudi [this message]
2024-04-15 21:17 ` Honnappa Nagarahalli
2024-04-15 22:19   ` Patrick Robb
2024-04-16  7:19     ` Thomas Monjalon

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=PAVPR08MB91853B3126B08A68692A2872EF092@PAVPR08MB9185.eurprd08.prod.outlook.com \
    --to=aditya.ambadipudi@arm.com \
    --cc=Dhruv.Tripathi@arm.com \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=ci@dpdk.org \
    --cc=wathsala.vithanage@arm.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).