All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [PATCH] eal: log hugepage create errors with filename
Date: Fri, 7 Jan 2022 11:53:21 +0000	[thread overview]
Message-ID: <YdgpsSdHKPVWCVDp@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20211223192158.143591-1-stephen@networkplumber.org>

On Thu, Dec 23, 2021 at 11:21:58AM -0800, Stephen Hemminger wrote:
> While debugging running DPDK service in a container, it is
> useful to see which file creation failed.  Don't hide this
> failure with DEBUG.
> 
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
>  lib/eal/linux/eal_memalloc.c | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
Acked-by: Bruce Richardson <bruce.richardson@intel.com>

Should we consider this a bugfix for backporting? Not printing the failing
path seems an omission that should be fixed generally.

  reply	other threads:[~2022-01-07 11:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-23 19:21 [PATCH] eal: log hugepage create errors with filename Stephen Hemminger
2022-01-07 11:53 ` Bruce Richardson [this message]
2022-01-21 14:26   ` 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=YdgpsSdHKPVWCVDp@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.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 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.