All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Sivaprasad Tummala <sivaprasad.tummala@amd.com>
Cc: <david.hunt@intel.com>, <anatoly.burakov@intel.com>,
	<thomas@monjalon.net>, <ferruh.yigit@amd.com>,
	<david.marchand@redhat.com>, <dev@dpdk.org>
Subject: Re: [RFC PATCH 1/2] power: fix power library with --lcores
Date: Wed, 24 Jul 2024 07:38:18 -0700	[thread overview]
Message-ID: <20240724073818.7c32899d@hermes.local> (raw)
In-Reply-To: <20240724130336.1076462-1-sivaprasad.tummala@amd.com>

On Wed, 24 Jul 2024 13:03:35 +0000
Sivaprasad Tummala <sivaprasad.tummala@amd.com> wrote:

> +		POWER_LOG(ERR, "Power library doesn't support lcore %u mapping "
> +				"to %u cpus", lcore_id, CPU_COUNT(&lcore_cpus));

Please don't break single format error string across lines. It makes it harder
for users to find the error in the source. Instead wrap after Er,,

  parent reply	other threads:[~2024-07-24 14:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-24 13:03 [RFC PATCH 1/2] power: fix power library with --lcores Sivaprasad Tummala
2024-07-24 13:03 ` [RFC PATCH 2/2] test/power: " Sivaprasad Tummala
2024-07-24 14:38 ` Stephen Hemminger [this message]
2024-07-24 14:39 ` [RFC PATCH 1/2] power: " Stephen Hemminger
2024-08-26 13:43   ` Tummala, Sivaprasad
2024-10-17 11:02 ` [PATCH v1 " Sivaprasad Tummala
2024-10-17 11:02   ` [PATCH v1 2/2] test/power: " Sivaprasad Tummala
2024-10-17 12:10     ` lihuisong (C)
2024-10-17 11:57   ` [PATCH v1 1/2] power: " Konstantin Ananyev
2024-10-17 12:05   ` lihuisong (C)
2024-10-18  2:52     ` Tummala, Sivaprasad
2024-10-18  3:34   ` [PATCH v2 " Sivaprasad Tummala
2024-10-18  3:34     ` [PATCH v2 2/2] test/power: " Sivaprasad Tummala
2024-10-18 10:15     ` [PATCH v2 1/2] power: " 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=20240724073818.7c32899d@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=anatoly.burakov@intel.com \
    --cc=david.hunt@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=sivaprasad.tummala@amd.com \
    --cc=thomas@monjalon.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.