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 X-Spam-Level: X-Spam-Status: No, score=-8.7 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_RED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D8402C433DB for ; Fri, 26 Feb 2021 13:01:25 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 897AC64D9F for ; Fri, 26 Feb 2021 13:01:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230155AbhBZNBJ (ORCPT ); Fri, 26 Feb 2021 08:01:09 -0500 Received: from mga05.intel.com ([192.55.52.43]:63566 "EHLO mga05.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229835AbhBZNBI (ORCPT ); Fri, 26 Feb 2021 08:01:08 -0500 IronPort-SDR: MKk+sjI6fkDf+qwPixYK9Uo0PiLGiPBrkvJHdM7xbBixYwUfKDBUqQd904N1s9bjFQMdW78qGT PWHuMg7nerLQ== X-IronPort-AV: E=McAfee;i="6000,8403,9906"; a="270843598" X-IronPort-AV: E=Sophos;i="5.81,208,1610438400"; d="scan'208";a="270843598" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga105.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 26 Feb 2021 04:59:20 -0800 IronPort-SDR: X1WOlhR3tq4jzAbAxzM37x9Ymi08+8tb1Aek+KRk5QedTqLUquA8ZW8F4+q8QosPOQqZ/QkWIe 9+WtZgWqzZZw== X-IronPort-AV: E=Sophos;i="5.81,208,1610438400"; d="scan'208";a="404893045" Received: from gna-dev.igk.intel.com (HELO localhost) ([10.102.80.34]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 26 Feb 2021 04:59:17 -0800 References: <20210216160525.5028-1-maciej.kwapulinski@linux.intel.com> <20210216160525.5028-2-maciej.kwapulinski@linux.intel.com> User-agent: mu4e 1.4.13; emacs 26.3 From: Maciej Kwapulinski To: Greg Kroah-Hartman Cc: Arnd Bergmann , Jonathan Corbet , Derek Kiernan , Dragan Cvetic , linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, Tomasz Jankowski , Savo Novakovic , Jianxun Zhang Subject: Re: [PATCH v1 01/12] gna: add driver module In-reply-to: Date: Fri, 26 Feb 2021 13:59:14 +0100 Message-ID: <85wnuvrnml.fsf@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-doc@vger.kernel.org Greg Kroah-Hartman writes: > On Tue, Feb 16, 2021 at 05:05:14PM +0100, Maciej Kwapulinski wrote: .... >> --- /dev/null >> +++ b/drivers/misc/gna/gna_driver.h >> @@ -0,0 +1,41 @@ >> +/* SPDX-License-Identifier: GPL-2.0-only */ >> +/* Copyright(c) 2017-2021 Intel Corporation */ >> + >> +#ifndef __GNA_DRIVER_H__ >> +#define __GNA_DRIVER_H__ >> + >> +#include >> +#include >> +#include >> + >> +#define GNA_DRV_NAME "gna" > > Way too generic, no one knows what "gna" is. > "intel gna" is much more verbose in search engines. As we do not (plan to) have more "gna" drivers, is the following ok?: intel-gna the change would imply the following: prompt$ lspci -s 00:00.3 -vvvv 00:00.3 System peripheral: Intel Corporation Device 3190 (rev 03) Subsystem: Intel Corporation Device 2072 .... Kernel driver in use: intel-gna Kernel modules: gna is it ok? also, how about the interface to library (it's part of one of next patches)?: prompt$ file /dev/gna0 /dev/gna0: character special (235/0) can "gna" stay intact here? I'm pointing this out, because gna exists on the market for a while and changing the above may have some impact we'd like to avoid. > ....