lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bc74cb1d-cd97-819c-5e0d-e9cd1e01dbf4@codeaurora.org>
Date:   Thu, 14 May 2020 18:43:06 -0600
From:   Jeffrey Hugo <jhugo@...eaurora.org>
To:     arnd@...db.de, gregkh@...uxfoundation.org
Cc:     manivannan.sadhasivam@...aro.org, bjorn.andersson@...aro.org,
        wufan@...eaurora.org, pratanan@...eaurora.org,
        linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 1/8] qaic: Add skeleton driver

On 5/14/2020 8:07 AM, Jeffrey Hugo wrote:
> +#define QAIC_NAME			"Qualcomm Cloud AI 100"
<snip>
> +static struct pci_driver qaic_pci_driver = {
> +	.name = QAIC_NAME,

A question about the community's preference here.

Our driver name is very verbose due to the desire to have the proper 
"branding".  However, I can see it being a bit obtuse, particularly in logs.

Would the community prefer something more succinct here, such as "qaic"?

-- 
Jeffrey Hugo
Qualcomm Technologies, Inc. is a member of the
Code Aurora Forum, a Linux Foundation Collaborative Project.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ