All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michel Dänzer" <michel-otUistvHUpPR7s880joybQ@public.gmane.org>
To: "Li, Samuel" <Samuel.Li-5C7GfCeVMHo@public.gmane.org>
Cc: "amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
	<amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>,
	"Yuan, Xiaojie" <Xiaojie.Yuan-5C7GfCeVMHo@public.gmane.org>
Subject: Re: [PATCH libdrm v4 1/1] amdgpu: move asic id table to a separate file
Date: Fri, 2 Jun 2017 12:05:39 +0900	[thread overview]
Message-ID: <b13d7f5c-85ea-aba2-bf1d-66d74f0a6e1b@daenzer.net> (raw)
In-Reply-To: <CY1PR1201MB10333653ACF093A7C38341EEF5F60-JBJ/M6OpXY+2VhmsawAdvGrFom/aUZj6nBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>

On 01/06/17 11:27 PM, Li, Samuel wrote:
>> If amdgpu.ids living in the amdgpu directory prevents it from being used by libdrm_radeon (why?), let's put it in a new toplevel directory, e.g.
>> "data".
>>> README is also located in this directory.
>> Not the same thing. It documents things about the header files, and doesn't get installed anywhere.
> I think that is a personal preference.

If you're referring to naming the new directory "data", that's just a
suggestion. Another possibility is to simply put it in the toplevel
directory.

What I wrote about include/drm/README is easily verifiable fact.


>>> My preference is to pass the names only, not to audit from a coder's 
>>> view ...
>> That's not how we do things.
> It is a data file, not really a part of code.

There is nothing magic about it. It's subject to the review process just
like any other file in the repository.

BTW, if you put the file outside of the amdgpu directory, you should
send the patch to the dri-devel mailing list for review as well.


> It shall be your preference to decide how much time you would like to
> spend in auditing the names :)

It shouldn't take as much time as we've spent talking about it in this
thread. :}


-- 
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:[~2017-06-02  3:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-29 21:16 [PATCH libdrm v4 1/1] amdgpu: move asic id table to a separate file Samuel Li
     [not found] ` <1496092589-10642-1-git-send-email-Samuel.Li-5C7GfCeVMHo@public.gmane.org>
2017-05-30  1:25   ` Michel Dänzer
     [not found]     ` <79a6b0a4-edb4-0368-1902-90458b577c1f-otUistvHUpPR7s880joybQ@public.gmane.org>
2017-05-30 22:31       ` Li, Samuel
     [not found]         ` <CY1PR1201MB1033195A941CEB02E9E93DB2F5F00-JBJ/M6OpXY+2VhmsawAdvGrFom/aUZj6nBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
2017-05-31  5:15           ` Michel Dänzer
     [not found]             ` <d4f0edae-8adf-50b1-e0b0-520b9e368e9c-otUistvHUpPR7s880joybQ@public.gmane.org>
2017-05-31 13:17               ` Alex Deucher
     [not found]                 ` <CADnq5_OZNgmVYeLyDBdzrvqLLKJ+EAKBq00K0WLFw+W1EnhgiQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-06-01  5:46                   ` Michel Dänzer
2017-05-31 15:32               ` Li, Samuel
     [not found]                 ` <CY1PR1201MB10336D98A57C23B8C3DF18A9F5F10-JBJ/M6OpXY+2VhmsawAdvGrFom/aUZj6nBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
2017-06-01  6:09                   ` Michel Dänzer
     [not found]                     ` <4cad0af4-94d0-0a74-7bfc-ef2e63227800-otUistvHUpPR7s880joybQ@public.gmane.org>
2017-06-01 14:27                       ` Li, Samuel
     [not found]                         ` <CY1PR1201MB10333653ACF093A7C38341EEF5F60-JBJ/M6OpXY+2VhmsawAdvGrFom/aUZj6nBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
2017-06-02  3:05                           ` Michel Dänzer [this message]
     [not found]                             ` <b13d7f5c-85ea-aba2-bf1d-66d74f0a6e1b-otUistvHUpPR7s880joybQ@public.gmane.org>
2017-06-02 14:25                               ` Li, Samuel

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=b13d7f5c-85ea-aba2-bf1d-66d74f0a6e1b@daenzer.net \
    --to=michel-otuistvhuppr7s880joybq@public.gmane.org \
    --cc=Samuel.Li-5C7GfCeVMHo@public.gmane.org \
    --cc=Xiaojie.Yuan-5C7GfCeVMHo@public.gmane.org \
    --cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@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.