Re: [PATCH RESEND v7 00/11] PCI: dwc: Relatively simple fixes and cleanups

[Serge Semin]

On Mon, Jun 12, 2023 at 12:16:08PM -0500, Bjorn Helgaas wrote:
> On Mon, Jun 12, 2023 at 07:41:24PM +0300, Serge Semin wrote:
> > On Mon, Jun 12, 2023 at 10:41:27AM -0500, Bjorn Helgaas wrote:
> > > On Sun, Jun 11, 2023 at 10:19:54PM +0300, Serge Semin wrote:
> > > > It turns out the recent DW PCIe-related patchset was merged in with
> > > > several relatively trivial issues left unsettled (noted by Bjorn and
> > > > Manivannan). All of these lefovers have been fixed in this patchset.
> > > > Namely the series starts with two bug-fixes. The first one concerns the
> > > > improper link-mode initialization in case if the CDM-check is enabled. The
> > > > second unfortunate mistake I made in the IP-core version type helper. In
> > > > particular instead of testing the IP-core version type the macro function
> > > > referred to the just IP-core version which obviously wasn't what I
> > > > intended.
> > > > ...
> > 
> > > I am unable to do anything with this series.
> > > 
> > > Google's legal team is reviewing this matter under applicable laws and
> > > regulations.
> > 
> > I don't get it, how come Google gets to decide anything about what to
> > do with this patchset?
> 

> I am employed by Google, and my Linux work is part of my job
> responsibility, so Google sets some boundaries on my activities.

Are you saying that Google can just like that affect the kernel
maintaining procedure by forcing their employees to ignore some other
developers work?  Nice, well done Google in "evolving" the open-source
community.

What do you suggest for us to do then? There are PCIe host and
endpoints drivers maintainers who aren't obligated by the Google
regulations: Lorenzo, Krzysztof, Rob. They are still able to merge the
series in to the PCI (or their own) repo since you are blocked by your
Google employer, right?

-Serge(y)

> 
> Bjorn