Linux CXL
 help / color / mirror / Atom feed
From: "Michal Suchánek" <msuchanek@suse.de>
To: Vishal Verma <vishal.l.verma@intel.com>
Cc: linux-cxl@vger.kernel.org, Dave Jiang <dave.jiang@intel.com>,
	Dan Williams <dan.j.williams@intel.com>,
	nvdimm@lists.linux.dev
Subject: Re: [PATCH ndctl 0/2] fix a couple of meson issues with v76
Date: Fri, 24 Feb 2023 10:06:34 +0100	[thread overview]
Message-ID: <20230224090634.GT19419@kitsune.suse.cz> (raw)
In-Reply-To: <20230223-meson-build-fixes-v1-0-5fae3b606395@intel.com>

On Thu, Feb 23, 2023 at 10:45:37PM -0700, Vishal Verma wrote:
> Fix the include paths for libtraceevent and libtracefs headers to not
> explicitly state the {lib}trace{fs,event}/ prefix since that is
> determined via pkg-config.
> 
> Require a minimum version of json-c for new APIs used by cxl-monitor.
> 
> Signed-off-by: Vishal Verma <vishal.l.verma@intel.com>
> ---
> Vishal Verma (2):
>       cxl/monitor: fix include paths for tracefs and traceevent
>       cxl/event-trace: use the wrapped util_json_new_u64()

Tested-by:  Michal Suchánek <msuchanek@suse.de>

Thanks

Michal

      parent reply	other threads:[~2023-02-24  9:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-24  5:45 [PATCH ndctl 0/2] fix a couple of meson issues with v76 Vishal Verma
2023-02-24  5:45 ` [PATCH ndctl 1/2] cxl/monitor: fix include paths for tracefs and traceevent Vishal Verma
2023-02-24  7:54   ` Ira Weiny
2023-02-24 15:29   ` Dave Jiang
2023-02-24  5:45 ` [PATCH ndctl 2/2] cxl/event-trace: use the wrapped util_json_new_u64() Vishal Verma
2023-02-24  7:55   ` Ira Weiny
2023-02-24 15:29   ` Dave Jiang
2023-02-24  9:06 ` Michal Suchánek [this message]

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=20230224090634.GT19419@kitsune.suse.cz \
    --to=msuchanek@suse.de \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=nvdimm@lists.linux.dev \
    --cc=vishal.l.verma@intel.com \
    /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