public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Moyer <jmoyer@redhat.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: linux-nvdimm@ml01.01.org, linux-acpi@vger.kernel.org,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	Robert Moore <robert.moore@intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [Linux-nvdimm] [PATCH v2 03/20] nd_acpi, nfit-test: manufactured NFITs for interface development
Date: Fri, 15 May 2015 16:25:34 -0400	[thread overview]
Message-ID: <x49pp61wptt.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <20150428182428.35812.95800.stgit@dwillia2-desk3.amr.corp.intel.com> (Dan Williams's message of "Tue, 28 Apr 2015 14:24:29 -0400")

Dan Williams <dan.j.williams@intel.com> writes:

> +config NFIT_TEST
> +	tristate "NFIT TEST: Manufactured NFIT for interface testing"
> +	depends on DMA_CMA
> +	depends on LIBND=m
> +	depends on ND_ACPI
> +	depends on m
> +	help
> +	  For development purposes register a manufactured
> +	  NFIT table to verify the resulting device model topology.
> +	  Note, this module arranges for ioremap_cache() to be
> +	  overridden locally to allow simulation of system-memory as an
> +	  io-memory-resource.
> +
> +	  Note, this test expects to be able to find at least 256MB of
> +	  CMA space (CONFIG_CMA_SIZE_MBYTES, cma=) or it will fail to
> +	  load.
> +
> +	  Say N unless you are doing development of the 'nd' subsystem.
> +

Too many TLAs.  I'm guessing CMA means Conventional Memory Area to you.
To me it means contiguous memory allocator.  Anyway, please define
acronyms when you use them, especially in help text.  The help text also
doesn't really explain where it will find this memory.  Would it be
possible to provide more direction there?

I don't have any useful commentary on the patch itself.  I do wonder if
you shouldn't move this to the end, as it's hardly an integral part of
the patch set.

Cheers,
Jeff

  reply	other threads:[~2015-05-15 20:25 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-28 18:24 [PATCH v2 00/20] libnd: non-volatile memory device support Dan Williams
2015-04-28 18:24 ` [PATCH v2 02/20] libnd, nd_acpi: initial libnd infrastructure and NFIT support Dan Williams
2015-04-30 23:23   ` Rafael J. Wysocki
2015-05-01  0:39     ` Dan Williams
2015-05-01  1:21       ` Rafael J. Wysocki
2015-05-01 16:23         ` Dan Williams
2015-05-04 23:58           ` Rafael J. Wysocki
2015-05-04 23:46             ` Dan Williams
2015-05-15 19:44   ` [Linux-nvdimm] " Jeff Moyer
2015-05-15 20:41     ` Dan Williams
2015-04-28 18:24 ` [PATCH v2 03/20] nd_acpi, nfit-test: manufactured NFITs for interface development Dan Williams
2015-05-15 20:25   ` Jeff Moyer [this message]
2015-05-15 20:50     ` [Linux-nvdimm] " Dan Williams
2015-04-28 18:24 ` [PATCH v2 04/20] libnd: ndctl class device, and nd bus attributes Dan Williams
2015-05-15 21:00   ` [Linux-nvdimm] " Jeff Moyer
2015-04-28 18:24 ` [PATCH v2 05/20] libnd, nd_acpi: dimm/memory-devices Dan Williams
2015-05-01 17:48   ` [Linux-nvdimm] " Toshi Kani
2015-05-01 18:22     ` Dan Williams
2015-05-01 18:19       ` Toshi Kani
2015-05-01 18:43         ` Dan Williams
2015-05-01 19:15           ` Toshi Kani
2015-05-01 19:38             ` Dan Williams
2015-05-01 20:08               ` Toshi Kani
2015-04-28 18:24 ` [PATCH v2 06/20] libnd: ndctl.h, the nd ioctl abi Dan Williams
2015-04-28 18:24 ` [PATCH v2 08/20] libnd, nd_acpi: regions (block-data-window, persistent memory, volatile memory) Dan Williams
2015-04-29 15:53   ` [Linux-nvdimm] " Elliott, Robert (Server Storage)
2015-04-29 15:59     ` Dan Williams
2015-05-04 20:26   ` Toshi Kani
2015-05-09 23:55     ` Dan Williams
2015-05-28 18:36       ` Toshi Kani
2015-05-28 19:59         ` Dan Williams
2015-05-28 20:51           ` Linda Knippers
2015-05-28 20:58             ` Dan Williams
2015-04-28 18:25 ` [PATCH v2 12/20] libnd, nd_acpi: add interleave-set state-tracking infrastructure Dan Williams
2015-04-28 20:52 ` [PATCH v2 00/20] libnd: non-volatile memory device support Andy Lutomirski
2015-04-28 20:59   ` Dan Williams
2015-04-28 21:06     ` Andy Lutomirski
2015-04-28 22:28       ` Dan Williams
2015-04-28 23:05         ` Andy Lutomirski
2015-04-30 20:56           ` Ross Zwisler
2015-04-28 21:24 ` [Linux-nvdimm] " Elliott, Robert (Server Storage)
2015-04-28 22:15   ` Dan Williams
2015-05-07  7:29     ` Christoph Hellwig
2015-04-29  0:25 ` Rafael J. Wysocki
2015-04-29  1:22   ` Dan Williams
2015-05-05  0:06     ` Rafael J. Wysocki
2015-05-08  6:31       ` Williams, Dan J

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=x49pp61wptt.fsf@segfault.boston.devel.redhat.com \
    --to=jmoyer@redhat.com \
    --cc=dan.j.williams@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvdimm@ml01.01.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=robert.moore@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