Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Archit Taneja <architt@codeaurora.org>
To: Sumit Semwal <sumit.semwal@linaro.org>,
	Daniel Stone <daniel@fooishbar.org>
Cc: Keith Packard <keithp@keithp.com>,
	Daniel Stone <daniels@collabora.com>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	DRI Development <dri-devel@lists.freedesktop.org>,
	Daniel Vetter <daniel.vetter@intel.com>,
	Tollef Fog Heen <tfheen@err.no>
Subject: Re: [PATCH] drm: Document code of conduct
Date: Tue, 11 Apr 2017 13:21:21 +0530	[thread overview]
Message-ID: <986a383c-3706-903a-7333-0a3b4193609c@codeaurora.org> (raw)
In-Reply-To: <CAO_48GGJ6OC-bSNOOtqipuFL5LrMcbZUr1zZatQeZtSv-iMPMw@mail.gmail.com>



On 04/11/2017 01:03 PM, Sumit Semwal wrote:
> On 11 April 2017 at 12:38, Daniel Stone <daniel@fooishbar.org> wrote:
>> Hi,
>>
>> On 11 April 2017 at 07:48, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
>>> Note: As Daniel Stone mentioned in the announcement fd.o admins
>>> started chatting with the communities their hosting, which includs the
>>> X.org foundation board, to figure out how to fan out enforcement and
>>> allow projects to run things on their own (with fd.o still as the
>>> fallback).  So the details of enforcement (and appealing decisions)
>>> might still change, but since this involves the board and lots more
>>> people it'll take a while to get there. For now this is good enough I
>>> think.
>>
>> All true.
>>
>> Reviewed-by: Daniel Stone <daniels@collabora.com>
>>
> Thanks for this, Daniel!
>
> Reviewed-by: Sumit Semwal <sumit.semwal@linaro.org>

Acked-by: Archit Taneja <architt@codeaurora.org>

Thanks,
Archit

>
> Best,
> Sumit.
>
>> Cheers,
>> Daniel
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
>

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-04-11  7:51 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-11  6:48 [PATCH] drm: Document code of conduct Daniel Vetter
2017-04-11  7:06 ` ✗ Fi.CI.BAT: warning for " Patchwork
2017-04-11  7:08 ` [PATCH] " Daniel Stone
2017-04-11  7:33   ` Sumit Semwal
2017-04-11  7:51     ` Archit Taneja [this message]
2017-04-11  8:25       ` [Intel-gfx] " Martin Peres
2017-04-12 12:59     ` Sumit Semwal
2017-04-11  9:03 ` Daniel Vetter
2017-04-11  9:52   ` Neil Armstrong
2017-04-12  9:35   ` Laurent Pinchart
2017-04-11  9:09 ` Chris Wilson
2017-04-11  9:19 ` Thierry Reding
2017-04-11  9:24 ` Jani Nikula
2017-04-11  9:43 ` Vincent ABRIOU
2017-04-11 10:01 ` Maarten Lankhorst
2017-04-11 10:04 ` Brian Starkey
2017-04-11 12:37 ` Rob Clark
2017-04-11 13:12 ` Luc Verhaegen
2017-04-11 13:24   ` Daniel Vetter
2017-04-11 13:30     ` Luc Verhaegen
2017-04-11 13:36       ` Daniel Vetter
2017-04-11 13:39         ` Luc Verhaegen
2017-04-11 13:58           ` Jani Nikula
2017-04-11 15:14             ` Luc Verhaegen
2017-04-11 15:31               ` Daniel Vetter
2017-04-11 15:48               ` Alex Deucher
2017-04-11 13:35 ` David Herrmann
2017-04-11 13:48 ` Sean Paul
2017-04-11 15:40 ` Harry Wentland
2017-04-11 15:50 ` Alex Deucher
2017-04-11 16:09   ` Daniel Vetter
2017-04-11 17:17     ` Alex Deucher
2017-04-11 16:19 ` Eric Anholt
2017-04-11 17:28 ` Gustavo Padovan
2017-04-12  9:26 ` Michel Dänzer
2017-04-12 13:34 ` Keith Packard
2017-04-14  2:43 ` Gabriel Krisman Bertazi

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=986a383c-3706-903a-7333-0a3b4193609c@codeaurora.org \
    --to=architt@codeaurora.org \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=daniel@fooishbar.org \
    --cc=daniels@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=keithp@keithp.com \
    --cc=sumit.semwal@linaro.org \
    --cc=tfheen@err.no \
    /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