All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michel Dänzer" <michel-otUistvHUpPR7s880joybQ@public.gmane.org>
To: "Marek Olšák" <maraeo-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	"Koenig,
	Christian" <Christian.Koenig-5C7GfCeVMHo@public.gmane.org>
Cc: amd-gfx mailing list
	<amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: Re: [PATCH libdrm] amdgpu: update amdgpu_drm.h
Date: Wed, 16 Jan 2019 18:24:02 +0100	[thread overview]
Message-ID: <a31b0bcf-0ba7-f276-e1b4-de862aa35959@daenzer.net> (raw)
In-Reply-To: <CAAxE2A5-q2hc6QugbtLU4n564263S6bemvmY_+VvapXeYmRcLg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On 2019-01-16 5:56 p.m., Marek Olšák wrote:
> On Wed, Jan 16, 2019 at 11:25 AM Koenig, Christian <Christian.Koenig@amd.com>
> wrote:
>> Am 16.01.19 um 17:15 schrieb Marek Olšák:
>> On Wed, Jan 16, 2019 at 2:37 AM Christian König <
>> ckoenig.leichtzumerken@gmail.com> wrote:
>>
>>> Am 15.01.19 um 20:25 schrieb Marek Olšák:
>>>> From: Marek Olšák <marek.olsak@amd.com>
>>>
>>> Maybe note in the commit message from which upstream kernel.
>>>
>>
>> No upstream kernel. It's from amd-staging-drm-next.
>>
>>
>> That's a problem, see the rules for updating this.
>>
>> IIRC the code must land in an upstream kernel before it can be committed
>> to libdrm.
>>
>> Christian.
>>
> 
> It looks like it's all in the master branch.

That's good, but please follow the procedure documented in
include/drm/README next time.


-- 
Earthling Michel Dänzer               |               http://www.amd.com
Libre software enthusiast             |             Mesa and X developer
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

      parent reply	other threads:[~2019-01-16 17:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-15 19:25 [PATCH libdrm] amdgpu: update amdgpu_drm.h Marek Olšák
     [not found] ` <20190115192527.11581-1-maraeo-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-01-16  7:37   ` Christian König
     [not found]     ` <92ca5d38-50d3-f00a-3750-b00fd11b6851-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-01-16 16:15       ` Marek Olšák
     [not found]         ` <CAAxE2A4Xz3DC7C7YV+GRSqznrRGBk7TCvpVk7pS+z+w80++XLA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-01-16 16:24           ` Koenig, Christian
     [not found]             ` <7b174535-ed89-9137-b204-dc21ca4ce896-5C7GfCeVMHo@public.gmane.org>
2019-01-16 16:55               ` Kazlauskas, Nicholas
2019-01-16 16:56               ` Marek Olšák
     [not found]                 ` <CAAxE2A5-q2hc6QugbtLU4n564263S6bemvmY_+VvapXeYmRcLg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-01-16 17:24                   ` Michel Dänzer [this message]

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=a31b0bcf-0ba7-f276-e1b4-de862aa35959@daenzer.net \
    --to=michel-otuistvhuppr7s880joybq@public.gmane.org \
    --cc=Christian.Koenig-5C7GfCeVMHo@public.gmane.org \
    --cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=maraeo-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 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.