Linux-NVDIMM Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "Williams, Dan J" <dan.j.williams@intel.com>
Cc: "linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: Re: [ndctl PATCH 0/7] introduce 'daxctl list', and 'ndctl list' updates
Date: Mon, 9 Jan 2017 22:05:40 +0000	[thread overview]
Message-ID: <1483999472.4414.0.camel@intel.com> (raw)
In-Reply-To: <CAPcyv4gUcb-Swm2t8yySq67BYBkoufBLE+vunionOLx2Rt_Oaw@mail.gmail.com>

On Mon, 2017-01-09 at 14:00 -0800, Dan Williams wrote:
> On Mon, Jan 9, 2017 at 1:56 PM, Vishal Verma <vishal.l.verma@intel.com
> > wrote:
> > On 01/06, Dan Williams wrote:
> > > * The 'ndctl list' command awkwardly prints out all the
> > > corresponding
> > >   device-dax information when a namespace is in 'dax' mode.
> > > Conversely if
> > >   someone is only interested in listing device-dax information
> > > they need to
> > >   contend with libnvdimm data.
> > > 
> > >   Introduce a separate daxctl utility with its own 'list' command
> > > for this
> > >   purpose, and make the listing of device-dax data through 'ndctl
> > > list'
> > >   optional (new --device-dax option).
> > 
> > the 'rpmbuild' script was failing as the new daxctl utility wasn't
> > included in %files in the spec. The following patch fixes that.
> > 
> > 8<-----
> > 
> > From d26a582b4ae9e69a22e52908a5d4bbae0a79717f Mon Sep 17 00:00:00
> > 2001
> > From: Vishal Verma <vishal.l.verma@intel.com>
> > Date: Mon, 9 Jan 2017 14:52:34 -0700
> > Subject: [PATCH] spec: add the new daxctl binary to the spec file
> > 
> > The missing binary was triggering the "installed but unpackaged file
> > found" check for rpmbuild. Add daxctl to the %files section as we do
> > want it to be packaged.
> 
> Yes, we do want it packaged, but in it's own rpm. I have patch to add
> that as well as a daxctl man page.

Ah ok - I thought it would just get installed as a part of the ndctl
rpm.
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

      reply	other threads:[~2017-01-09 22:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-07  1:42 [ndctl PATCH 0/7] introduce 'daxctl list', and 'ndctl list' updates Dan Williams
2017-01-07  1:42 ` [ndctl PATCH 1/7] ndctl, daxctl: refactor main boilerplate for a new 'daxctl' utility Dan Williams
2017-01-07  1:42 ` [ndctl PATCH 2/7] ndctl, daxctl: move json helpers to be available across both utilities Dan Williams
2017-01-07  1:42 ` [ndctl PATCH 3/7] ndctl, list: add option to filter namespace by mode Dan Williams
2017-01-07  1:42 ` [ndctl PATCH 4/7] ndctl, list: add '--device-dax' option Dan Williams
2017-01-07  1:42 ` [ndctl PATCH 5/7] daxctl: add list command Dan Williams
2017-01-07  1:42 ` [ndctl PATCH 6/7] ndctl, {enable,disable}-region: filter by type Dan Williams
2017-01-07  1:42 ` [ndctl PATCH 7/7] ndctl, list: limit mappings when --dimm is specified Dan Williams
2017-01-09 21:56 ` [ndctl PATCH 0/7] introduce 'daxctl list', and 'ndctl list' updates Vishal Verma
2017-01-09 22:00   ` Dan Williams
2017-01-09 22:05     ` Verma, Vishal L [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=1483999472.4414.0.camel@intel.com \
    --to=vishal.l.verma@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=linux-nvdimm@lists.01.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox