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  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Wed, 9 Sep 2020 08:36:37 +0200 (CEST)
From:   Jiri Kosina <jikos@...nel.org>
To:     Sean O'Brien <seobrien@...omium.org>
cc:     Benjamin Tissoires <benjamin.tissoires@...hat.com>,
        linux-input@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
        Wei-Ning Huang <wnhuang@...gle.com>
Subject: Re: [PATCH v2] HID: google: add google vivaldi HID driver

On Wed, 26 Aug 2020, Sean O'Brien wrote:

> > I actually believe we should follow the standard convention here, and have
> > just one hid-<vendor> driver for all google products. Currently we have
> > hid-google-hammer, and this would add hid-google-vivaldi. Would you (or
> > Wei-Ning, CCing here) object on merging these two together?
> 
> I'm a bit reluctant to merge them.  Partly because I'm not familiar with
> the hid-google-hammer driver, but mostly because this driver is intended
> to handle non-google products which will use a google-defined usage code.
> Perhaps I should drop "google" from the driver name?

If it's known that it will be handling non-google products, then I think 
that's indeed the best option. Thanks in advance for v3 with this change,

-- 
Jiri Kosina
SUSE Labs

Powered by blists - more mailing lists