From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:44092) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zlsp1-0005VH-4A for qemu-devel@nongnu.org; Tue, 13 Oct 2015 02:12:28 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Zlsox-0000uL-3n for qemu-devel@nongnu.org; Tue, 13 Oct 2015 02:12:27 -0400 Received: from mga02.intel.com ([134.134.136.20]:61546) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zlsow-0000sP-S1 for qemu-devel@nongnu.org; Tue, 13 Oct 2015 02:12:23 -0400 References: <1444535584-18220-1-git-send-email-guangrong.xiao@linux.intel.com> <1444535584-18220-24-git-send-email-guangrong.xiao@linux.intel.com> <20151012133853-mutt-send-email-mst@redhat.com> <561C92EE.60609@linux.intel.com> <20151013082734-mutt-send-email-mst@redhat.com> From: Xiao Guangrong Message-ID: <561C9F50.9040605@linux.intel.com> Date: Tue, 13 Oct 2015 14:06:08 +0800 MIME-Version: 1.0 In-Reply-To: <20151013082734-mutt-send-email-mst@redhat.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v3 23/32] nvdimm: build ACPI NFIT table List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" Cc: ehabkost@redhat.com, kvm@vger.kernel.org, gleb@kernel.org, mtosatti@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com, imammedo@redhat.com, pbonzini@redhat.com, dan.j.williams@intel.com, rth@twiddle.net On 10/13/2015 01:42 PM, Michael S. Tsirkin wrote: > On Tue, Oct 13, 2015 at 01:13:18PM +0800, Xiao Guangrong wrote: >>> >>>> #endif >>> >>> This header is too small to be worth it. >>> nvdimm_get_built_list seems to be the only interface - >>> just stick it in the header you have under include. >>> >> >> Other functions are introudced and included into it in later patches, >> it includes the internal things shared between nvdimm device, nvdimm ACPI, >> nvdimm namespace. >> >> Furthermore, this is a internal include file, it is not bad i think. > > Each time we do this, this seems to invite abuse where > people add APIs without documenting them. > Understood. > I guess I could buy this if you add nvdimm_defs.h > with just internal things such as layout of the buffer > used for communication between ACPI and hardware. > Okay, i will rename internel.h to nvdimm_defs.h and carefully document everything (definitions, function prototypes, etc.) in this file. :)