All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gabriel Krisman Bertazi <krisman@collabora.co.uk>
To: amy.shih@advantech.com.tw
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [Bug 101044] I915 driver caused VGA got no ignal after plug-out then plug-in the VGA cable
Date: Mon, 15 May 2017 10:16:19 -0300	[thread overview]
Message-ID: <87wp9ib6qk.fsf@dilma.collabora.co.uk> (raw)
In-Reply-To: <bug-101044-502@http.bugs.freedesktop.org/> (bugzilla-daemon@freedesktop.org's message of "Mon, 15 May 2017 02:13:32 +0000")

bugzilla-daemon@freedesktop.org writes:

>  Bug ID     101044
>  Summary    I915 driver caused VGA got no ignal after plug-out then
>             plug-in the VGA cable
>  Product    Mesa
>  Version    unspecified
>  Hardware   Other
>  OS         Linux (All)
>  Status     NEW
>  Severity   normal
>  Priority   highest
>  Component  Drivers/DRI/i915
>  Assignee   dri-devel@lists.freedesktop.org
>  Reporter   amy.shih@advantech.com.tw
>  QA Contact dri-devel@lists.freedesktop.org
>  Group      Mesa Security

Is there any reason why this is reported against Mesa Security team?
This is stopping me from replying, since I don't have access to Mesa
Security bugs.

It feels like you should have reported it against the DRI product and
DRM/Intel component, since it looks like a DRM driver bug.

--
Gabriel Krisman Bertazi
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2017-05-15 13:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-15  2:13 [Bug 101044] I915 driver caused VGA got no ignal after plug-out then plug-in the VGA cable bugzilla-daemon
2017-05-15 13:16 ` Gabriel Krisman Bertazi [this message]
2017-05-16  1:16 ` bugzilla-daemon

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=87wp9ib6qk.fsf@dilma.collabora.co.uk \
    --to=krisman@collabora.co.uk \
    --cc=amy.shih@advantech.com.tw \
    --cc=dri-devel@lists.freedesktop.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.