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
Date: Tue, 7 Mar 2017 16:33:46 +0000 [thread overview]
Message-ID: <20170307163346.GA2255@ct-lt-587> (raw)
In-Reply-To: <87o9xdf4ek.fsf@intel.com>
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
next prev parent reply other threads:[~2017-03-07 16:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 14:27 [PATCH 0/2] Documentation/EDID fixes Javi Merino
2017-03-06 14:27 ` [PATCH 1/2] drm: use .hword to represent 16-bit numbers Javi Merino
2017-03-06 14:27 ` [PATCH 2/2] drm: Add O= support Javi Merino
2017-03-07 16:16 ` [PATCH 0/2] Documentation/EDID fixes Jani Nikula
2017-03-07 16:33 ` Javi Merino [this message]
2017-03-08 8:11 ` Jani Nikula
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=20170307163346.GA2255@ct-lt-587 \
--to=javi.merino@kernel.org \
--cc=C.Emde@osadl.org \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@lists.codethink.co.uk \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox