From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:49182) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UwotT-0005sn-II for qemu-devel@nongnu.org; Wed, 10 Jul 2013 03:32:57 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UwotS-0003Tt-OD for qemu-devel@nongnu.org; Wed, 10 Jul 2013 03:32:55 -0400 Received: from mail-pb0-f50.google.com ([209.85.160.50]:62328) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UwotS-0003Tk-IA for qemu-devel@nongnu.org; Wed, 10 Jul 2013 03:32:54 -0400 Received: by mail-pb0-f50.google.com with SMTP id wz7so6433837pbc.37 for ; Wed, 10 Jul 2013 00:32:53 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: From: Peter Maydell Date: Wed, 10 Jul 2013 08:32:33 +0100 Message-ID: Content-Type: text/plain; charset=UTF-8 Subject: Re: [Qemu-devel] [PATCH v1 3/4] target-arm/helper.c: Allow const opaques in arm CP List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: peter.crosthwaite@xilinx.com Cc: qemu-devel@nongnu.org On 10 July 2013 05:22, wrote: > From: Peter Crosthwaite > > Allow for defining const opaque data in ARM CP register definitions by > setting .opaque = foo. If non null opaque is passes into > define_one_arm_cp_reg_with_opaque then that opaque will take > precedence, otherwise if null opaque is passed, the original opaque > data will be used. This doesn't seem to have any motivating use in later patches in the series, or did I miss it? I guess being able to have the opaque data in the data-tables is nice, though. thanks -- PMM