Received: by 2002:a25:1985:0:0:0:0:0 with SMTP id 127csp3273046ybz; Mon, 27 Apr 2020 13:06:52 -0700 (PDT) X-Google-Smtp-Source: APiQypIc7giFFyIG9vLxod6SZcTA3rNG+5h4h9Fh1+B6pNyIWrdpCXp7AAFNHf01oTX7b5hHNhAJ X-Received: by 2002:a17:906:2acf:: with SMTP id m15mr20543854eje.173.1588018011982; Mon, 27 Apr 2020 13:06:51 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1588018011; cv=none; d=google.com; s=arc-20160816; b=kjQb3logJSXSH6ttZxi6w4c2XcVskORfRjShqsevMfVegykOU+BLmShq/POcaj82rP ypubUy+xtHY6UGobr9zbi8oQO6O0Awq8/gbPwGVDSKF6KUDjgCaxKRbhAuxFwchd/RGF C+B07qwEm5yefrqpSCHkrxuLGIaIjgsATgVBTYDseWiDAbWadiVx2QNOjJBrVLolvKiP GWyfpdWTmMAPLduKgJTjg+tvQYkxaOy/jaeIe0tekVg08VYYSaM9XJcO/DvzLFUoIJ8N UtEYN8+1BnB1InfdkeojX8aE37oQHmbDPOm1rWUjsc5ydG2kEVo0cAVWR5fOcev3dHiB uxSQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:date:cc:to:from:subject:message-id :ironport-sdr:ironport-sdr; bh=iP9uPsiVLm4wtULDeJPtTFaDu4Zr4SE3hpgZkiQzEs0=; b=XKfN3HWCvmGbjU2PfJA4zKcfKVxLoxnH7k7fsnRr0jDnfwW/7EFobc+xPaTmCej/Al eHqDh6vWn03Y6qm+ZCKI65n3XnIDKX+jS/2ZVbp0xwXstmvUVcKrHJVjMOCL0Z0c11NT ipBirEv/K98DgdcY631YkgPKZSC5nTIph7knkQC7/7zx7qSX6LcmCbU9bWF5yOO04oNb ChFMcE0krHW/9+ZAVvG1ZC7wy5tM8oLi+tJf3HxpOo3o1vonS4zjDRMvarsUJKJlnIiy xTfbwxPAtXKzvNH2BEr4erCH/iiSqp+OyGOD7Yj6Thpabuw2xuC0esaot969mZSl+ihD r9DA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id b21si341748edj.146.2020.04.27.13.06.28; Mon, 27 Apr 2020 13:06:51 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726456AbgD0UCu (ORCPT + 99 others); Mon, 27 Apr 2020 16:02:50 -0400 Received: from mga03.intel.com ([134.134.136.65]:39874 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725919AbgD0UCu (ORCPT ); Mon, 27 Apr 2020 16:02:50 -0400 IronPort-SDR: xyhOBZkl21/qbGBfznK57qFUK7MTGpmCEXRCe6DtBqlNBSkNub++q9R9llCcrFOYEty5E9I9ue c56ONvCzCJcA== X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 27 Apr 2020 13:02:49 -0700 IronPort-SDR: GjYAFcoCqlm+a4DLVaIJAvUAkzUxehDUWIlKKkNGv15CoC9Gjm0QebAmw4Fh+1XvSlidfKCs59 jTk3opP0EgeQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.73,325,1583222400"; d="scan'208";a="458979574" Received: from coffy.sc.intel.com ([10.3.79.166]) by fmsmga006.fm.intel.com with ESMTP; 27 Apr 2020 13:02:49 -0700 Message-ID: <01620c87bb6aa7870854ae1e23ec7bd379a058de.camel@intel.com> Subject: Re: [PATCH v2 0/1] platform/x86: Add Slim Bootloader firmware update support From: Jithu Joseph To: Andy Shevchenko Cc: Darren Hart , Andy Shevchenko , Platform Driver , Linux Kernel Mailing List , maurice.ma@intel.com, ravi.p.rangarajan@intel.com, Sean V Kelley , kuo-lang.tseng@intel.com, jithu.joseph@intel.com Date: Mon, 27 Apr 2020 12:57:05 -0700 In-Reply-To: References: <20200423224222.29730-1-jithu.joseph@intel.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5-0ubuntu0.18.04.1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2020-04-27 at 13:03 +0300, Andy Shevchenko wrote: > > > We use a bit different template for module names > > vendor-...-wmi > > (yes, with exception to TBT) > > I would like to rename sbl_fwu_wmi to something like this: > > intel-wmi-sbl-fw-update > > What do you think? Yes I think it is better to rename this driver to intel-wmi-sbl-fw- update as you suggested, given many drivers follow vendor-wmi-* pattern. Thanks for pointing this out. I will send v3 which addresses this. Thanks Jithu