From: Rob Pearce <rob@flitspace.org.uk>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
David Airlie <airlied@linux.ie>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] INTEL DRM DRIVERS : No LVDS hardware on Intel D410PT and D425KT
Date: Sun, 27 Oct 2013 18:29:32 +0000 [thread overview]
Message-ID: <526D5B8C.7090904@flitspace.org.uk> (raw)
In-Reply-To: <20131027173302.GA25812@kroah.com>
On 27/10/13 17:33, Greg KH wrote:
> On Sun, Oct 27, 2013 at 04:13:42PM +0000, Rob Pearce wrote:
>> From: Rob Pearce <rob@flitspace.org.uk>
>>
>> The Intel D410PT(LW) and D425KT Mini-ITX desktop boards both show up as
>> having LVDS but the hardware is not populated. This patch adds them to
>> the list of such systems. Patch is against 3.11.4
>>
>> Signed-off-by: Rob Pearce <rob@flitspace.org.uk>
>> ---
>> Patch revised to match the D425KT exactly as the D425KTW does have LVDS.
>> According to Intel's documentation, the D410PTL and D410PLTW don't.
>
> Any reason you don't want this in the stable tree as well?
>
No, should be in stable. Sorry, I'm obviously getting some etiquette
wrong (this is the first patch I've submitted).
Cheers,
Rob
next prev parent reply other threads:[~2013-10-27 18:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-27 16:13 [PATCH] INTEL DRM DRIVERS : No LVDS hardware on Intel D410PT and D425KT Rob Pearce
2013-10-27 17:33 ` Greg KH
2013-10-27 18:07 ` Daniel Vetter
2013-10-27 18:29 ` Rob Pearce [this message]
2013-10-27 18:35 ` Guenter Roeck
2013-10-27 19:29 ` Daniel Vetter
-- strict thread matches above, loose matches on Subject: below --
2013-10-27 13:35 Rob Pearce
2013-10-27 13:51 ` Daniel Vetter
2013-10-27 16:06 ` Rob Pearce
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=526D5B8C.7090904@flitspace.org.uk \
--to=rob@flitspace.org.uk \
--cc=airlied@linux.ie \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=intel-gfx@lists.freedesktop.org \
--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