Date: Tue, 7 Mar 2017 16:33:46 +0000
From: Javi Merino <javi.merino@kernel.org>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: airlied@linux.ie, C.Emde@osadl.org, linux-kernel@lists.codethink.co.uk,
        linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/2] Documentation/EDID fixes
Message-ID: <20170307163346.GA2255@ct-lt-587>
References: <1488810456-4583-1-git-send-email-javi.merino@kernel.org>
 <87o9xdf4ek.fsf@intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <87o9xdf4ek.fsf@intel.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 698
Lines: 17

On Tue, Mar 07, 2017 at 06:16:51PM +0200, Jani Nikula wrote:
> On Mon, 06 Mar 2017, Javi Merino <javi.merino@kernel.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.

Cheers,
Javi