From: Daniel Vetter <daniel@ffwll.ch>
To: Hans de Goede <hdegoede@redhat.com>
Cc: David Airlie <airlied@linux.ie>, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm: panel-orientation-quirks: Add quirk for Lenovo Ideapad Mixx 310
Date: Wed, 25 Apr 2018 09:05:31 +0200 [thread overview]
Message-ID: <20180425070530.GI25142@phenom.ffwll.local> (raw)
In-Reply-To: <e9077581-c0f0-feaa-34a4-2677b520b28c@redhat.com>
On Tue, Apr 24, 2018 at 02:24:59PM +0200, Hans de Goede wrote:
> Hi,
>
> On 24-04-18 14:18, Daniel Vetter wrote:
> > On Tue, Apr 24, 2018 at 12:26:04PM +0200, Maarten Lankhorst wrote:
> > > Op 24-04-18 om 12:09 schreef Hans de Goede:
> > > > Hi,
> > > >
> > > > On 18-04-18 14:36, Hans de Goede wrote:
> > > > > Some production batches of the Lenovo Ideapad Mixx 310 laptop use
> > > > > a portrait LCD panel, add a quirk for this.
> > > > >
> > > > > Signed-off-by: Hans de Goede <hdegoede@redhat.com>
> > > >
> > > > Ping?
> > > >
> > > > Can I please get an ack for these 2 trivial patches to that I can
> > > > push them to drm-misc-next ?
> > > >
> > > > Thanks & Regards,
> > > I don't have the hw, but patches look sane..
> > >
> > > Reviewed-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> >
> > For quirks, bugzilla/reporter/any other evidence why we need it would be
> > really good. If you haven't pushed yet, pls add that.
>
> Sorry, too late. I must admit I'm a bit of a hoarder when it
> comes to BYT / CHT hardware (as I spend my spare time on trying
> to make those work properly with Linux) and I own all devices
> currently listed, except for the GPD Pocket which I borrowed
> from a friend for a while to get it supported properly under
> Linux.
>
> But I'm currently emailing with someone who has a device with
> a non-upright mounted LCD-panel which will need a quirk too,
> which will be the first device I don't have access to myself.
Ah ok, as long as all we need to figure this out is nag you I think it's
ok. We've had plenty of cases in the past where it looked like quirk
entries just papered over a driver bug (which we discovered much later),
so it's good if there's some way to get hold of the original reporters
again. Even if chances are generally slim.
> I will add his email address as a comment to the entry when I
> submit the patch for that.
Commit message is prefectly fine.
Thanks, Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2018-04-25 7:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 12:36 [PATCH 1/2] drm: panel-orientation-quirks: Add quirk for Lenovo Ideapad Mixx 310 Hans de Goede
2018-04-18 12:36 ` [PATCH 2/2] drm: panel-orientation-quirks: Add quirk for Lenovo Ideapad Mixx 320 Hans de Goede
2018-04-24 10:09 ` [PATCH 1/2] drm: panel-orientation-quirks: Add quirk for Lenovo Ideapad Mixx 310 Hans de Goede
2018-04-24 10:26 ` Maarten Lankhorst
2018-04-24 11:47 ` Hans de Goede
2018-04-24 12:18 ` Daniel Vetter
2018-04-24 12:24 ` Hans de Goede
2018-04-25 7:05 ` Daniel Vetter [this message]
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=20180425070530.GI25142@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=hdegoede@redhat.com \
/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