[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <82DABEC7F9941D458E51BA62B2739EF437ADDC68@sun1049.dh.corp>
Date: Thu, 15 Nov 2018 08:37:47 +0000
From: Christoph Niedermaier <cniedermaier@...electronics.de>
To: Jonathan Corbet <corbet@....net>
CC: "linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
"C.Emde@...dl.org" <C.Emde@...dl.org>
Subject: Re: [PATCH 0/2] Docs/EDID: Fixed and improved EDID documentation
Hi Jon,
On Tue, Nov 6, 2018, Jonathan Corbet wrote:
> This seems reasonable, I guess; I've applied both. It seems to me, though,
> that this stuff is in the wrong place. Perhaps we should go one step
> further and move it to tools/ ?
I spoke to Carsten and his intention apparently was to merely document
how the somewhat cryptic data structures in drivers/gpu/drm/drm_edid_load.c
were derived. The code needed to be run only once to generate the data and
never again. So it not really is a tool that someone may want to run from time
to time for a particular purpose. So we would propose to leave the EDID directory
where it currently is. However, should you feel that it would better be placed
in the tools directory then you certainly may do that.
Best regards,
Christoph
Powered by blists - more mailing lists