Content-Type: multipart/mixed; boundary="===============2718165539593699090==" MIME-Version: 1.0 From: Dave Jiang Subject: [Accel-config] Re: [PATCH] accel-config: Update doc with a json file format requirement Date: Mon, 28 Jun 2021 15:16:45 -0700 Message-ID: <8ed25229-cec0-1ddd-869f-a30f06eccbd0@intel.com> In-Reply-To: 20210628195519.1029662-1-ramesh.thomas@intel.com To: accel-config@lists.01.org List-ID: --===============2718165539593699090== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On 6/28/2021 12:55 PM, ramesh.thomas(a)intel.com wrote: > From: Ramesh Thomas > > Config files use json format which uses keys for each object. Mention in > manpages that the "dev" property is used as the key and must be the firt > entry in each object block. > > Signed-off-by: Ramesh Thomas Reviewed-by: Dave Jiang Should put giant warning about not hand craft json files and let the = tool do it. > --- > Documentation/accfg/accel-config-load-config.txt | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/Documentation/accfg/accel-config-load-config.txt b/Documenta= tion/accfg/accel-config-load-config.txt > index 23867ff..53ea01d 100644 > --- a/Documentation/accfg/accel-config-load-config.txt > +++ b/Documentation/accfg/accel-config-load-config.txt > @@ -21,6 +21,9 @@ like, but it should not be used directly given the vari= ance of each system. The > user should create a proper config file according to the format of samp= le file > and use "-c" option to point to the config file. > = > +The "dev" property is used as the key for each json object and must be t= he > +first entry in each object block. > + > EXAMPLE > ------- > ---- --===============2718165539593699090==--