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 7E555C433FE for ; Thu, 29 Sep 2022 18:11:52 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230001AbiI2SLv (ORCPT ); Thu, 29 Sep 2022 14:11:51 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43480 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232402AbiI2SLt (ORCPT ); Thu, 29 Sep 2022 14:11:49 -0400 Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2286E1E459B; Thu, 29 Sep 2022 11:11:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1664475109; x=1696011109; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=Hi2tz7dvkDqO9KGRG9jxKLr4Lwuxpc+amCA8E8qTyfY=; b=kwPk69LahIVQbrC99oxQrpOzjYJoVLsqqPHRMWUraRrs+JBrGm5T/wYG HM6O/V+wvryih12fDRrWPzFQT+5kvJSOkgGplSxNTHkJQ4v6km+6i1w4q IMAVt0POwyGP4drlI9gQO17qT0LDfQlElLGQAe2z/pX53Z0B5UiV+zP6F sVLcm6WKMPjvnjbXVa3NFfFPHCvy37ytMdD2WrckbCoKBzrYuZHozNChA /PaPXET/KhdFTVSxcTpjWsR6tRhsXUNbeqhtieYx80lNX03JUf4r7ZaR4 uQ7cuD3FZD3a+DaqU13cx7czs5+DQ5N/3lfEhx1hq1UUkrxLFMiEw+Rb7 w==; X-IronPort-AV: E=McAfee;i="6500,9779,10485"; a="282347587" X-IronPort-AV: E=Sophos;i="5.93,355,1654585200"; d="scan'208";a="282347587" Received: from orsmga006.jf.intel.com ([10.7.209.51]) by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Sep 2022 11:11:48 -0700 X-IronPort-AV: E=McAfee;i="6500,9779,10485"; a="600106659" X-IronPort-AV: E=Sophos;i="5.93,355,1654585200"; d="scan'208";a="600106659" Received: from tjthomps-mobl.amr.corp.intel.com (HELO [10.252.139.94]) ([10.252.139.94]) by orsmga006-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Sep 2022 11:11:48 -0700 Message-ID: <665a4db2-a342-43ba-38a0-715c34709729@linux.intel.com> Date: Thu, 29 Sep 2022 11:11:47 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Firefox/91.0 Thunderbird/91.11.0 Subject: Re: [PATCH v14 2/3] virt: Add TDX guest driver Content-Language: en-US To: Wander Lairson Costa Cc: Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , x86@kernel.org, Shuah Khan , Jonathan Corbet , "H . Peter Anvin" , Greg Kroah-Hartman , "Kirill A . Shutemov" , Tony Luck , Kai Huang , Isaku Yamahata , marcelo.cerri@canonical.com, tim.gardner@canonical.com, khalid.elmously@canonical.com, philip.cox@canonical.com, linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org, linux-doc@vger.kernel.org References: <20220928215535.26527-1-sathyanarayanan.kuppuswamy@linux.intel.com> <20220928215535.26527-3-sathyanarayanan.kuppuswamy@linux.intel.com> From: Sathyanarayanan Kuppuswamy In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-doc@vger.kernel.org On 9/29/22 11:02 AM, Wander Lairson Costa wrote: >> +#define TDX_GUEST_DEVICE "tdx-guest" > nit: I think now we can use KBUILD_MODNAME, can't we? > Yes. We can use it. But I thought user can use this macro and avoid hard coding the device name. -- Sathyanarayanan Kuppuswamy Linux Kernel Developer