From: Daniel Vetter <daniel@ffwll.ch>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Rob Pearce <rob@flitspace.org.uk>,
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 19:07:06 +0100 [thread overview]
Message-ID: <20131027180706.GJ18189@phenom.ffwll.local> (raw)
In-Reply-To: <20131027173302.GA25812@kroah.com>
On Sun, Oct 27, 2013 at 10:33:02AM -0700, 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?
None. Picked up for -fixes, thanks for the patch. Also I prefer the patch
change log in the commit message proper and less screaming in the summary
;-) All fixed while applying.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2013-10-27 18:07 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 [this message]
2013-10-27 18:29 ` Rob Pearce
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=20131027180706.GJ18189@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--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 \
--cc=rob@flitspace.org.uk \
/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.