[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87r328chn2.fsf@intel.com>
Date: Wed, 08 Mar 2017 10:11:29 +0200
From: Jani Nikula <jani.nikula@...ux.intel.com>
To: Javi Merino <javi.merino@...nel.org>
Cc: airlied@...ux.ie, C.Emde@...dl.org,
linux-kernel@...ts.codethink.co.uk, linux-kernel@...r.kernel.org,
dri-devel@...ts.freedesktop.org
Subject: Re: [PATCH 0/2] Documentation/EDID fixes
On Tue, 07 Mar 2017, Javi Merino <javi.merino@...nel.org> wrote:
> On Tue, Mar 07, 2017 at 06:16:51PM +0200, Jani Nikula wrote:
>> On Mon, 06 Mar 2017, Javi Merino <javi.merino@...nel.org> wrote:
>> > I found these two minor issues while building an EDID. I'm not sure
>> > whether the second patch (Add O= to support) is upstream material, but
>> > I'm sending it just in case.
>>
>> I'm not opposed to fixing existing issues like this, but really I think
>> there should be an userspace tool for this. Definitely outside of the
>> Documentation directory, perhaps even outside the kernel tree
>> altogether.
>
> I am not sure whether this should be in the kernel or not, but I
> agree that Documentation/ doesn't look like the right place to build
> these files.
Just so there's no confusion: I'm just saying what I think should be
done in the long run. I'm not opposed to the fixes at hand, but someone
else needs to review them.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
Powered by blists - more mailing lists