From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:57895) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cimAv-0001vx-Ud for qemu-devel@nongnu.org; Tue, 28 Feb 2017 13:07:03 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cimAv-0002dG-5q for qemu-devel@nongnu.org; Tue, 28 Feb 2017 13:07:01 -0500 Date: Tue, 28 Feb 2017 19:06:56 +0100 From: Kevin Wolf Message-ID: <20170228180656.GY4090@noname.redhat.com> References: <1488194450-28056-1-git-send-email-armbru@redhat.com> <1488194450-28056-24-git-send-email-armbru@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1488194450-28056-24-git-send-email-armbru@redhat.com> Subject: Re: [Qemu-devel] [PATCH 23/24] keyval: Restrict key components to valid QAPI names List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Markus Armbruster Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org, pkrempa@redhat.com, eblake@redhat.com Am 27.02.2017 um 12:20 hat Markus Armbruster geschrieben: > Restricting the key components to something sane leaves us room for > evolving key syntax. Since they will be commonly used as QAPI member > names by the QObject input visitor, we can just as well borrow the > QAPI naming rules here. > > Signed-off-by: Markus Armbruster Reviewed-by: Kevin Wolf