From: Jani Nikula <jani.nikula@linux.intel.com>
To: airlied@linux.ie, C.Emde@osadl.org
Cc: linux-kernel@lists.codethink.co.uk,
Javi Merino <javi.merino@kernel.org>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/2] Documentation/EDID fixes
Date: Tue, 07 Mar 2017 18:16:51 +0200 [thread overview]
Message-ID: <87o9xdf4ek.fsf@intel.com> (raw)
In-Reply-To: <1488810456-4583-1-git-send-email-javi.merino@kernel.org>
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.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Javi Merino <javi.merino@kernel.org>, airlied@linux.ie, C.Emde@osadl.org
Cc: linux-kernel@lists.codethink.co.uk,
Javi Merino <javi.merino@kernel.org>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/2] Documentation/EDID fixes
Date: Tue, 07 Mar 2017 18:16:51 +0200 [thread overview]
Message-ID: <87o9xdf4ek.fsf@intel.com> (raw)
In-Reply-To: <1488810456-4583-1-git-send-email-javi.merino@kernel.org>
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.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2017-03-07 16:16 UTC|newest]
Thread overview: 8+ 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 ` Jani Nikula [this message]
2017-03-07 16:16 ` [PATCH 0/2] Documentation/EDID fixes Jani Nikula
2017-03-07 16:33 ` Javi Merino
2017-03-08 8:11 ` Jani Nikula
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=87o9xdf4ek.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=C.Emde@osadl.org \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=javi.merino@kernel.org \
--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 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.