From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7E870CCA473 for ; Wed, 6 Jul 2022 17:17:19 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233691AbiGFRRS (ORCPT ); Wed, 6 Jul 2022 13:17:18 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39336 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233705AbiGFRRR (ORCPT ); Wed, 6 Jul 2022 13:17:17 -0400 Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5EE2F2A737; Wed, 6 Jul 2022 10:17:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1657127831; x=1688663831; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=k/GJ1Ocu6NSTbZWVHRMDXxNhqdLrEsXDfyhMdsiS/Fk=; b=BDxWCV0EK4dz8dFSd90CjRwejnvf4mqYI5mhhMHVU40Ht7BI0+JmowO4 30mWzAjWt4PcgVZ0zlJTHwlbrpMPCzVn5kEzTt7LEGs+FShaTrc/Dr1P3 7G739puc/lylZTUmKK9T3rNq6YcvdGOOQmroBLHxpk4zvPxPD1Jnh5dAT PoR3XoOWc+F6dgm/1dAnMbU+W2sm9DHCymWscMMvp6PtqQRMUCzumb8u8 7qfCbLdeADErd0gIFVPudS8W8MMwX9Ee50BEJiynWWf9/YZDtl0/xRUad PS1HwjoYXVZGZEo5gZxWOSathufC8KzPQfitrTQWic3sf2CZQyTMMPaqO A==; X-IronPort-AV: E=McAfee;i="6400,9594,10400"; a="370134896" X-IronPort-AV: E=Sophos;i="5.92,250,1650956400"; d="scan'208";a="370134896" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga105.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 06 Jul 2022 10:17:10 -0700 X-IronPort-AV: E=Sophos;i="5.92,250,1650956400"; d="scan'208";a="620415107" Received: from tjsteven-mobl3.amr.corp.intel.com (HELO [10.255.228.25]) ([10.255.228.25]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 06 Jul 2022 10:17:10 -0700 Message-ID: <2a2411f0-60a9-cf7d-b34d-b1756ad499a5@intel.com> Date: Wed, 6 Jul 2022 10:15:05 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.1 Subject: Re: [PATCH 04/22] x86/sgx: fix kernel-doc markups Content-Language: en-US To: Mauro Carvalho Chehab , Linux Doc Mailing List Cc: "H. Peter Anvin" , Jonathan Corbet , Mauro Carvalho Chehab , Borislav Petkov , Dave Hansen , Ingo Molnar , Jarkko Sakkinen , Thomas Gleixner , linux-kernel@vger.kernel.org, linux-sgx@vger.kernel.org, x86@kernel.org References: <49f0900ca467867917182a4428b731e55608ca67.1656409369.git.mchehab@kernel.org> From: Dave Hansen In-Reply-To: <49f0900ca467867917182a4428b731e55608ca67.1656409369.git.mchehab@kernel.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-doc@vger.kernel.org On 6/28/22 02:46, Mauro Carvalho Chehab wrote: > + * @rdi: snapshot of DI register at enclave exit > + * @rsi: snapshot of SI register at enclave exit > + * @rdx: snapshot of DX register at enclave exit > + * @rsp: snapshot of SP register at enclave exit > + * @r8: snapshot of R8 register at enclave exit > + * @r9: snapshot of R9 register at enclave exit The 'DX register' really is different than RDX. These should all have the full register names, like: snapshot of RSP register at enclave exit With that fixed: Acked-by: Dave Hansen