DPDK patches and discussions
 help / color / mirror / Atom feed
From: Pavel Shirshov <pavel.shirshov@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH] lib/librte_power: Fix typos
Date: Fri, 10 Nov 2017 00:18:29 -0800	[thread overview]
Message-ID: <1510301909-18848-1-git-send-email-pavel.shirshov@gmail.com> (raw)

Signed-off-by: Pavel Shirshov <pavel.shirshov@gmail.com>
---
 lib/librte_power/rte_power_acpi_cpufreq.c | 4 ++--
 lib/librte_power/rte_power_acpi_cpufreq.h | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/lib/librte_power/rte_power_acpi_cpufreq.c b/lib/librte_power/rte_power_acpi_cpufreq.c
index 01ac5ac..6b0cdb2 100644
--- a/lib/librte_power/rte_power_acpi_cpufreq.c
+++ b/lib/librte_power/rte_power_acpi_cpufreq.c
@@ -267,7 +267,7 @@ power_get_available_freqs(struct rte_power_info *pi)
 	}
 
 	ret = 0;
-	POWER_DEBUG_TRACE("%d frequencie(s) of lcore %u are available\n",
+	POWER_DEBUG_TRACE("%d frequency(s) of lcore %u are available\n",
 			count, pi->lcore_id);
 out:
 	fclose(f);
@@ -359,7 +359,7 @@ rte_power_acpi_cpufreq_init(unsigned lcore_id)
 	}
 
 	RTE_LOG(INFO, POWER, "Initialized successfully for lcore %u "
-			"power manamgement\n", lcore_id);
+			"power management\n", lcore_id);
 	rte_atomic32_cmpset(&(pi->state), POWER_ONGOING, POWER_USED);
 
 	return 0;
diff --git a/lib/librte_power/rte_power_acpi_cpufreq.h b/lib/librte_power/rte_power_acpi_cpufreq.h
index eee0ca0..bc20dfd 100644
--- a/lib/librte_power/rte_power_acpi_cpufreq.h
+++ b/lib/librte_power/rte_power_acpi_cpufreq.h
@@ -180,7 +180,7 @@ int rte_power_acpi_cpufreq_freq_max(unsigned lcore_id);
  *
  * @return
  *  - 1 on success with frequency changed.
- *  - 0 on success without frequency chnaged.
+ *  - 0 on success without frequency changed.
  *  - Negative on error.
  */
 int rte_power_acpi_cpufreq_freq_min(unsigned lcore_id);
-- 
2.7.4

                 reply	other threads:[~2017-11-10  8:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1510301909-18848-1-git-send-email-pavel.shirshov@gmail.com \
    --to=pavel.shirshov@gmail.com \
    --cc=dev@dpdk.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;
as well as URLs for NNTP newsgroup(s).