From: Mario Limonciello <mario.limonciello@amd.com>
To: <linux-firmware@kernel.org>, Josh Boyer <jwboyer@kernel.org>
Cc: Mario Limonciello <mario.limonciello@amd.com>
Subject: [PATCH 06/20] qca: correct typographical errors in NOTICE.txt caught by codespell
Date: Tue, 15 Aug 2023 13:00:04 -0500 [thread overview]
Message-ID: <20230815180018.25554-7-mario.limonciello@amd.com> (raw)
In-Reply-To: <20230815180018.25554-1-mario.limonciello@amd.com>
Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
---
qca/NOTICE.txt | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/qca/NOTICE.txt b/qca/NOTICE.txt
index 93130207..fde2a7c8 100644
--- a/qca/NOTICE.txt
+++ b/qca/NOTICE.txt
@@ -199,7 +199,7 @@ File Name list: aes.h, aes_locl.h
*
* @version 3.0 (December 2000)
*
- * Optimised ANSI C code for the Rijndael cipher (now AES)
+ * Optimized ANSI C code for the Rijndael cipher (now AES)
*
* @author Vincent Rijmen <vincent.rijmen@esat.kuleuven.ac.be>
* @author Antoon Bosselaers <antoon.bosselaers@esat.kuleuven.ac.be>
@@ -243,7 +243,7 @@ when who what, where, why
I retain copyright in this code but I encourage its free use provided
that I don't carry any responsibility for the results. I am especially
happy to see it used in free and open source software. If you do use
- it I would appreciate an acknowledgement of its origin in the code or
+ it I would appreciate an acknowledgment of its origin in the code or
the product that results and I would also appreciate knowing a liitle
about the use to which it is being put.
@@ -274,7 +274,7 @@ when who what, where, why
I retain copyright in this code but I encourage its free use provided
that I don't carry any responsibility for the results. I am especially
happy to see it used in free and open source software. If you do use
- it I would appreciate an acknowledgement of its origin in the code or
+ it I would appreciate an acknowledgment of its origin in the code or
the product that results and I would also appreciate knowing a liitle
about the use to which it is being put.
--
2.25.1
next prev parent reply other threads:[~2023-08-15 18:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 17:59 [PATCH 00/20] Add preparations to be able to run in a CI/CD system Mario Limonciello
2023-08-15 17:59 ` [PATCH 01/20] ath11k: update typographical errors in the Notice.txt files Mario Limonciello
2023-08-15 18:00 ` [PATCH 02/20] ath10k: correct " Mario Limonciello
2023-08-15 18:00 ` [PATCH 03/20] i915: correct typographical errors caught by codespell Mario Limonciello
2023-08-15 18:00 ` [PATCH 04/20] adsp_sst: " Mario Limonciello
2023-08-15 18:00 ` [PATCH 05/20] agere: correct typographical errors in LICENSE " Mario Limonciello
2023-08-15 18:00 ` Mario Limonciello [this message]
2023-08-15 18:00 ` [PATCH 07/20] usbdux: correct typographical errors " Mario Limonciello
2023-08-15 18:00 ` [PATCH 08/20] dsp56k: correct typographical error " Mario Limonciello
2023-08-15 18:00 ` [PATCH 09/20] cxgb4: correct typographical errors " Mario Limonciello
2023-08-15 18:00 ` [PATCH 10/20] cavium_liquidio: fix " Mario Limonciello
2023-08-15 18:00 ` [PATCH 11/20] kaweth: correct " Mario Limonciello
2023-08-15 18:00 ` [PATCH 12/20] xc5000c: " Mario Limonciello
2023-08-15 18:00 ` [PATCH 13/20] qcom: " Mario Limonciello
2023-08-15 18:00 ` [PATCH 14/20] keyspan_pda: " Mario Limonciello
2023-08-15 18:00 ` [PATCH 15/20] carl9170fw: " Mario Limonciello
2023-08-15 18:00 ` [PATCH 16/20] WHENCE: " Mario Limonciello
2023-08-15 18:00 ` [PATCH 17/20] check_whence: reformat using python black Mario Limonciello
2023-08-15 18:00 ` [PATCH 18/20] Add CI/CD with ci-fairy Mario Limonciello
2023-08-15 18:00 ` [PATCH 19/20] Wire up pre-commit to `make check` Mario Limonciello
2023-08-15 18:00 ` [PATCH 20/20] Rewrite README in markdown Mario Limonciello
2023-08-25 17:22 ` [PATCH 00/20] Add preparations to be able to run in a CI/CD system Dmitry Baryshkov
2023-08-28 11:15 ` Josh Boyer
2023-08-30 15:51 ` Mario Limonciello
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=20230815180018.25554-7-mario.limonciello@amd.com \
--to=mario.limonciello@amd.com \
--cc=jwboyer@kernel.org \
--cc=linux-firmware@kernel.org \
/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