From: Dave Jiang <dave.jiang@intel.com>
To: Vishal Verma <vishal.l.verma@intel.com>, linux-cxl@vger.kernel.org
Cc: nvdimm@lists.linux.dev
Subject: Re: [PATCH ndctl] ndctl.spec.in: Add build dependencies for libtraceevent and libtracefs
Date: Wed, 22 Feb 2023 14:25:21 -0700 [thread overview]
Message-ID: <345cdc01-dbb2-fac9-ccfb-d18d50be375d@intel.com> (raw)
In-Reply-To: <20230222-fix-rpm-spec-v1-1-e6d8668ea421@intel.com>
On 2/22/23 1:20 PM, Vishal Verma wrote:
> The cxl-monitor additions pull in new dependencies on libtraceevent and
> libtracefs. While the commits below added these to the meson build
> system, they neglected to also update the RPM spec file. Add them to
> the spec.
>
> Fixes: 8dedc6cf5e85 ("cxl: add a helper to parse trace events into a json object")
> Fixes: 7b237bc7a8ae ("cxl: add a helper to go through all current events and parse them")
> Cc: Dave Jiang <dave.jiang@intel.com>
> Signed-off-by: Vishal Verma <vishal.l.verma@intel.com>
Reviewed-by: Dave Jiang <dave.jiang@intel.com>
> ---
> ndctl.spec.in | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/ndctl.spec.in b/ndctl.spec.in
> index 35c63e6..0543c48 100644
> --- a/ndctl.spec.in
> +++ b/ndctl.spec.in
> @@ -31,6 +31,8 @@ BuildRequires: keyutils-libs-devel
> BuildRequires: systemd-rpm-macros
> BuildRequires: iniparser-devel
> BuildRequires: meson
> +BuildRequires: libtraceevent-devel
> +BuildRequires: libtracefs-devel
>
> %description
> Utility library for managing the "libnvdimm" subsystem. The "libnvdimm"
>
> ---
> base-commit: 835b09602cdcae8d324eeaf5bb4f17ae959c5e6d
> change-id: 20230222-fix-rpm-spec-2edf5a7fc25b
>
> Best regards,
prev parent reply other threads:[~2023-02-22 21:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 20:20 [PATCH ndctl] ndctl.spec.in: Add build dependencies for libtraceevent and libtracefs Vishal Verma
2023-02-22 20:22 ` Dan Williams
2023-02-22 21:25 ` Dave Jiang [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=345cdc01-dbb2-fac9-ccfb-d18d50be375d@intel.com \
--to=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 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.