linux-kernel - Re: [PATCH v3 0/4] HID: touchscreen: add himax hid-over-spi driver

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Thu, 18 Jan 2024 15:06:56 -0800
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Cc: Doug Anderson <dianders@...omium.org>,
	Tylor Yang <tylor_yang@...ax.corp-partner.google.com>,
	Tomasz Figa <tfiga@...omium.org>, jingyliang@...omium.org,
	poyuan_chang@...ax.corp-partner.google.com, hbarnor@...omium.org,
	jikos@...nel.org, wuxy23@...ovo.com, conor+dt@...nel.org,
	luolm1@...ovo.com, robh+dt@...nel.org, devicetree@...r.kernel.org,
	krzysztof.kozlowski+dt@...aro.org,
	poyu_hung@...ax.corp-partner.google.com,
	linux-kernel@...r.kernel.org, linux-input@...r.kernel.org,
	benjamin.tissoires@...hat.com
Subject: Re: [PATCH v3 0/4] HID: touchscreen: add himax hid-over-spi driver

On Wed, Oct 18, 2023 at 08:07:32AM +0200, Krzysztof Kozlowski wrote:
> On 17/10/2023 23:41, Doug Anderson wrote:
> > 
> > 3. The ChromeOS team is organized much more like the upstream
> > community than a big hierarchical corporation. Just as it's not easy
> > for you to control the behavior of other maintainers, it is not
> > trivial for one person on the team to control what others on the team
> > will do. We could make an attempt to institute rules like "all patches
> > must go through internal review before being posted", but as per #2 I
> > don't think this is a good idea. The ChromeOS team has even less
> > control over what our partners may or may not do. In general it is
> > always a struggle to get partners to even start working upstream and
> > IMO it's a win when I see a partner post a patch. We should certainly
> > help partners be successful here, but the right way to do that is by
> > offering them support.
> 
> I don't know who is exactly core team, who is partner. I see
> "google.com" domain, so Google folks are responsible for not wasting
> time of the community. If Google disagrees, please change the domain so
> I will understand that and not feel like Google wants to use us all.

I think it might help if you think of <company>.corp-partner.google.com
addresses as gmail.com addresses. People who are using these addresses
are not employees of Google nor contractors for Google; they work for
their respective <company>.

The main reason person@<company>.corp-partner.google.com addresses are
being used for mainline submissions is because it is actually possible
to set up "git send-email" with them, as their main domain typically
handled by Exchange and mandates Outlook.

Thanks.

-- 
Dmitry