From: Mark Brown <broonie@kernel.org>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Greg KH <gregkh@linuxfoundation.org>,
ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Challenges in Upstream vs. Embargoed Development in Intel Graphics.
Date: Wed, 5 Sep 2018 12:13:58 +0100 [thread overview]
Message-ID: <20180905111358.GH9781@sirena.org.uk> (raw)
In-Reply-To: <CAKMK7uEJfgACdzLdfh+EeG-NFkr47Bn3PFWCEOPA+1D1=5J7kA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 895 bytes --]
On Wed, Sep 05, 2018 at 10:17:44AM +0200, Daniel Vetter wrote:
> This was an invitation to exchange experience in how to best deal with
> the fallout - I do actually know that this is not an intel-only issue
> because I chatted with non-Intel people about how they deal with this.
It's definitely not an Intel only problem, I know I worked with this
when I was at a chip vendor and I know there are Linaro members with
various approaches to this.
> And I thought that figuring out how to do better upstream-first is
> very much within the scope of ks/lpc, hence why I suggested Rodrigo
> brings this up as a talk proposal.
I agree that there's a valuable discussion to have. So long as people
are selling physical chips I don't think we can realistically tell
people that they should just upstream everything immediately without
regard for marketing, lead customer relationships and so on.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-09-05 11:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 19:54 Rodrigo Vivi
2018-09-05 4:22 ` Leon Romanovsky
2018-09-05 4:49 ` Rodrigo Vivi
2018-09-05 7:38 ` Leon Romanovsky
2018-09-05 7:48 ` Greg KH
2018-09-05 8:17 ` Daniel Vetter
2018-09-05 8:31 ` Greg KH
2018-09-05 9:00 ` Daniel Vetter
2018-09-05 9:34 ` Leon Romanovsky
2018-09-05 22:45 ` Rodrigo Vivi
2018-09-06 13:56 ` Leon Romanovsky
2018-09-05 11:21 ` Mark Brown
2018-09-06 9:54 ` Linus Walleij
2018-09-06 10:15 ` Jani Nikula
2018-09-06 10:27 ` Mark Brown
2018-09-06 10:25 ` Arnd Bergmann
2018-09-06 10:43 ` Linus Walleij
2018-09-06 10:51 ` Mark Brown
2018-09-06 12:49 ` Sean Paul
2018-09-06 16:00 ` Jon Masters
2018-09-06 20:41 ` Rodrigo Vivi
2018-09-06 20:35 ` Rodrigo Vivi
2018-09-05 11:13 ` Mark Brown [this message]
2018-09-05 7:48 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2018-09-04 17:42 Rodrigo Vivi
2018-09-06 20:09 ` Rodrigo Vivi
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=20180905111358.GH9781@sirena.org.uk \
--to=broonie@kernel.org \
--cc=daniel.vetter@ffwll.ch \
--cc=gregkh@linuxfoundation.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox