All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Jani Nikula <jani.nikula@intel.com>
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>,
	ksummit-discuss@lists.linuxfoundation.org,
	Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Challenges in Upstream vs. Embargoed Development in Intel Graphics.
Date: Thu, 6 Sep 2018 11:27:51 +0100	[thread overview]
Message-ID: <20180906102751.GC5360@sirena.org.uk> (raw)
In-Reply-To: <87va7jylra.fsf@intel.com>

[-- Attachment #1: Type: text/plain, Size: 767 bytes --]

On Thu, Sep 06, 2018 at 01:15:53PM +0300, Jani Nikula wrote:
> On Thu, 06 Sep 2018, Linus Walleij <linus.walleij@linaro.org> wrote:

> > - Classify the components into embargoed and non-embargoed
> >   so anything not affected by embargo can be pushed upstream.
> >   (OK it's maybe obvious).

> It should be obvious, but given the dual mode of operation, people tend
> to err on the side of caution, and you need to constantly have an eye
> out for stuff that should be refactored and sent to upstream directly.

I suspect this is harder for things like the i915 driver where divisions
are less clear but it's usually fairly easy for things like SoCs or more
standalone chips where you're typically working with completely separate
drivers that are easy to segment.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2018-09-06 10:27 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-04 19:54 [Ksummit-discuss] [MAINTAINERS SUMMIT] Challenges in Upstream vs. Embargoed Development in Intel Graphics 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 [this message]
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
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=20180906102751.GC5360@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jani.nikula@intel.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=rodrigo.vivi@intel.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.