From: Jani Nikula <jani.nikula@linux.intel.com>
To: Enrico Deotto <E.Deotto@gds.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: bug (driver i915) in kernel >= 4.9.40
Date: Mon, 12 Feb 2018 12:13:47 +0200 [thread overview]
Message-ID: <87lgfy7bxg.fsf@intel.com> (raw)
In-Reply-To: <VI1PR1001MB1151130461E54E1B1720DF0E8FF20@VI1PR1001MB1151.EURPRD10.PROD.OUTLOOK.COM>
On Fri, 09 Feb 2018, Enrico Deotto <E.Deotto@gds.com> wrote:
> I'm writing you to get more info about a possible bug we are
> experiencing on kernel 4.9 (details below). If this is not the proper
> address please accept my apologies and let me know where I should
> address my request to.
Please file a bug at [1], with the info from this mail.
Thanks,
Jani.
[1] https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Intel
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2018-02-12 10:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 13:35 bug (driver i915) in kernel >= 4.9.40 Enrico Deotto
2018-02-12 10:13 ` Jani Nikula [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=87lgfy7bxg.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=E.Deotto@gds.com \
--cc=intel-gfx@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox