Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751465AbdFFN42 (ORCPT ); Tue, 6 Jun 2017 09:56:28 -0400 Received: from mail-wm0-f43.google.com ([74.125.82.43]:38791 "EHLO mail-wm0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751388AbdFFN40 (ORCPT ); Tue, 6 Jun 2017 09:56:26 -0400 Date: Tue, 6 Jun 2017 15:56:21 +0200 From: Pali =?utf-8?B?Um9ow6Fy?= To: Mario.Limonciello@dell.com Cc: luto@amacapital.net, dvhart@infradead.org, platform-driver-x86@vger.kernel.org, andriy.shevchenko@linux.intel.com, luto@kernel.org, rjw@rjwysocki.net, linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org Subject: Re: [PATCH 15/16] platform/x86: wmi-mof: New driver to expose embedded WMI MOF metadata Message-ID: <20170606135621.GC4690@pali> References: <201705271314.16241@pali> <20170605221456.GA27270@fury> <201706060019.26462@pali> <20170606110554.GB4690@pali> <8aa135f430b441eb82614b22d662d1ff@ausx13mpc120.AMER.DELL.COM> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <8aa135f430b441eb82614b22d662d1ff@ausx13mpc120.AMER.DELL.COM> User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1117 Lines: 24 On Tuesday 06 June 2017 13:46:16 Mario.Limonciello@dell.com wrote: > Pali, > > Amazing job with what you've done so far. A few comments I wanted to share from my taking look at your bmf2mof and comparing to "source" MOF. > 1) At least in source the case used for String and Boolean is lower case. I'm unsure if that actually matters for any MOF parsing tools, but I wanted to FYI in case it does. In MS documentation is String, Boolean and Datetime with first char uppercase. But looks like mofcomp accept both upper case and lower case variants. > 2) On my system when you expand the arguments for "void DoBFn" the source doesn't describe individual arguments like you do. > Again this might not matter to MOF parsing tools but wanted to let you know in case it does. I know, this part is missing. Order of arguments are only in ID qualifier and not sorted + in/out de-duplicated. > source: > void DoBFn([in, out, Description("Fn buf")] BDat Data); > bmf2mof: > void doBFn([in, Description("Fn buf"), ID(0)] BDat Data, [out, Description("Fn buf"), ID(0)] BDat Data); -- Pali Rohár pali.rohar@gmail.com