All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Doug Anderson <dianders@chromium.org>,
	Tylor Yang <tylor_yang@himax.corp-partner.google.com>,
	Tomasz Figa <tfiga@chromium.org>,
	jingyliang@chromium.org,
	poyuan_chang@himax.corp-partner.google.com, hbarnor@chromium.org,
	jikos@kernel.org, wuxy23@lenovo.com, conor+dt@kernel.org,
	luolm1@lenovo.com, robh+dt@kernel.org,
	devicetree@vger.kernel.org, krzysztof.kozlowski+dt@linaro.org,
	poyu_hung@himax.corp-partner.google.com,
	linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
	benjamin.tissoires@redhat.com
Subject: Re: [PATCH v3 0/4] HID: touchscreen: add himax hid-over-spi driver
Date: Thu, 18 Jan 2024 15:06:56 -0800	[thread overview]
Message-ID: <ZamvEAGGiDrQvmFq@google.com> (raw)
In-Reply-To: <9e1233ce-1a6d-443d-873e-6efb3ed0207c@linaro.org>

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

  parent reply	other threads:[~2024-01-18 23:07 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-17  9:18 [PATCH v3 0/4] HID: touchscreen: add himax hid-over-spi driver Tylor Yang
2023-10-17  9:18 ` [PATCH v3 1/4] dt-bindings: input: Introduce Himax HID-over-SPI device Tylor Yang
2023-10-17 13:59   ` Conor Dooley
2023-10-17 16:58     ` Krzysztof Kozlowski
2023-10-17  9:18 ` [PATCH v3 2/4] HID: touchscreen: Add initial support for Himax HID-over-SPI Tylor Yang
2023-10-17 17:01   ` Krzysztof Kozlowski
2023-10-18  7:15   ` Benjamin Tissoires
2023-10-18 10:14   ` kernel test robot
2023-10-17  9:18 ` [PATCH v3 3/4] " Tylor Yang
2023-10-18  7:23   ` Benjamin Tissoires
2023-10-17  9:19 ` [PATCH v3 4/4] " Tylor Yang
2023-10-17 17:03   ` Krzysztof Kozlowski
2023-10-19  3:51   ` kernel test robot
2023-10-19  6:47   ` kernel test robot
2023-10-17 17:08 ` [PATCH v3 0/4] HID: touchscreen: add himax hid-over-spi driver Krzysztof Kozlowski
2023-10-17 21:41   ` Doug Anderson
2023-10-18  6:07     ` Krzysztof Kozlowski
2023-10-18  6:33       ` Benjamin Tissoires
2024-01-18 23:06       ` Dmitry Torokhov [this message]
2024-01-22  4:57   ` Tomasz Figa
2024-01-22  8:08     ` Krzysztof Kozlowski
2024-01-22 13:57       ` Tomasz Figa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZamvEAGGiDrQvmFq@google.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=hbarnor@chromium.org \
    --cc=jikos@kernel.org \
    --cc=jingyliang@chromium.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luolm1@lenovo.com \
    --cc=poyu_hung@himax.corp-partner.google.com \
    --cc=poyuan_chang@himax.corp-partner.google.com \
    --cc=robh+dt@kernel.org \
    --cc=tfiga@chromium.org \
    --cc=tylor_yang@himax.corp-partner.google.com \
    --cc=wuxy23@lenovo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.