From: "Hunt, David" <david.hunt@intel.com>
To: <dev@dpdk.org>
Subject: Re: [PATCH v1 1/3] examples/power: remove empty poll mode from l3fwd-power
Date: Tue, 20 Dec 2022 13:26:01 +0000 [thread overview]
Message-ID: <493af91a-0e2a-6191-c032-757d27ca297e@intel.com> (raw)
In-Reply-To: <20221220125614.29493-2-david.hunt@intel.com>
On 20/12/2022 12:56, David Hunt wrote:
> Remove calls to the experimental empty poll API. l3fwd-power
> is the only app that uses this.
>
> This API is no longer needed as it is superceded by the
> monitor/pause/scale callback mechanism.
>
I did check the spelling against my spellchecker with checkpatch, and it
was clean. Too bad my dictionary uses a disputed spelling...
From https://www.merriam-webster.com/dictionary/supercede: "Supercede
has occurred as a spelling variant of supersede since the 17th century,
and it is common in current published writing. It continues, however, to
be widely regarded as an error."
I'll fix in the next patch revision.
Rgds,
Dave.
next prev parent reply other threads:[~2022-12-20 13:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 12:56 power: remove experimental empty poll API David Hunt
2022-12-20 12:56 ` [PATCH v1 1/3] examples/power: remove empty poll mode from l3fwd-power David Hunt
2022-12-20 13:26 ` Hunt, David [this message]
2023-02-07 10:47 ` Pattan, Reshma
2023-02-08 10:48 ` [PATCH v2 0/3] power: remove experimental empty poll API David Hunt
2023-02-08 10:48 ` [PATCH v2 1/3] examples/power: remove empty poll mode from l3fwd-power David Hunt
2023-02-08 11:11 ` Pattan, Reshma
2023-02-08 10:48 ` [PATCH v2 2/3] libs/power: remove experimental empty poll API David Hunt
2023-02-08 10:48 ` [PATCH v2 3/3] doc/power: remove empty poll documentation David Hunt
2023-02-19 23:53 ` [PATCH v2 0/3] power: remove experimental empty poll API Thomas Monjalon
2022-12-20 12:56 ` [PATCH v1 2/3] libs/power: " David Hunt
2023-02-07 11:04 ` Pattan, Reshma
2022-12-20 12:56 ` [PATCH v1 3/3] doc/power: remove empty poll documentation David Hunt
2023-02-07 10:06 ` Pattan, Reshma
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=493af91a-0e2a-6191-c032-757d27ca297e@intel.com \
--to=david.hunt@intel.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).