From: Marc Herbert <Marc.Herbert@intel.com>
To: alison.schofield@intel.com, nvdimm@lists.linux.dev
Cc: Michal Suchanek <msuchanek@suse.de>
Subject: Re: [ndctl PATCH] cxl/json: remove prefix from tracefs.h #include
Date: Tue, 11 Feb 2025 09:14:09 -0800 [thread overview]
Message-ID: <89603666-3c31-4689-b0bc-e558e6aa5b22@intel.com> (raw)
In-Reply-To: <20250209180348.1773179-1-alison.schofield@intel.com>
On 2025-02-09 10:03, alison.schofield@intel.com wrote:
> From: Michal Suchanek <msuchanek@suse.de>
>
> Distros vary on whether tracefs.h is placed in {prefix}/libtracefs/
> or {prefix}/tracefs/. Since the library ships with pkgconfig info
> to determine the exact include path the #include statement can drop
> the tracefs/ prefix.
>
> This was previously found and fixed elsewhere:
> a59866328ec5 ("cxl/monitor: fix include paths for tracefs and traceevent")
> but was introduced anew with cxl media-error support in ndctl v80.
>
> Reposted here from github pull request:
> https://github.com/pmem/ndctl/pull/268/
>
> [ alison: commit msg and log edits ]
>
> Fixes: 9873123fce03 ("cxl/list: collect and parse media_error records")
> Signed-off-by: Michal Suchanek <msuchanek@suse.de>
> Signed-off-by: Alison Schofield <alison.schofield@intel.com>
> ---
> cxl/json.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Marc Herbert <marc.herbert@intel.com>
> diff --git a/cxl/json.c b/cxl/json.c
> index 5066d3bed13f..e65bd803b706 100644
> --- a/cxl/json.c
> +++ b/cxl/json.c
> @@ -9,7 +9,7 @@
> #include <json-c/json.h>
> #include <json-c/printbuf.h>
> #include <ccan/short_types/short_types.h>
> -#include <tracefs/tracefs.h>
> +#include <tracefs.h>
>
> #include "filter.h"
> #include "json.h"
>
> base-commit: 04815e5f8b87e02a4fb5a61aeebaa5cad25a15c3
next prev parent reply other threads:[~2025-02-11 17:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-09 18:03 [ndctl PATCH] cxl/json: remove prefix from tracefs.h #include alison.schofield
2025-02-11 17:14 ` Marc Herbert [this message]
2025-02-12 16:11 ` Dave Jiang
2025-03-03 19:59 ` Alison Schofield
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=89603666-3c31-4689-b0bc-e558e6aa5b22@intel.com \
--to=marc.herbert@intel.com \
--cc=alison.schofield@intel.com \
--cc=msuchanek@suse.de \
--cc=nvdimm@lists.linux.dev \
/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.