From: Ian Pilcher <arequipeno@gmail.com>
To: stable@vger.kernel.org
Subject: Re: How to report regression in stable tree?
Date: Sun, 31 Dec 2017 16:20:58 -0600 [thread overview]
Message-ID: <p2bnoe$v7q$1@blaine.gmane.org> (raw)
In-Reply-To: <1514673702.2714.138.camel@decadent.org.uk>
On 12/30/2017 04:41 PM, Ben Hutchings wrote:
> For i915, I think you should either:
> - open a bug at bugs.freedesktop.org (under DRI, DRM/Intel)
> - mail intel-gfx@lists.freedesktop.org and cc stable
Done.
https://bugs.freedesktop.org/show_bug.cgi?id=104425
--
========================================================================
Ian Pilcher arequipeno@gmail.com
-------- "I grew up before Mark Zuckerberg invented friendship" --------
========================================================================
next prev parent reply other threads:[~2017-12-31 22:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-30 19:16 How to report regression in stable tree? Ian Pilcher
2017-12-30 22:41 ` Ben Hutchings
2017-12-31 22:20 ` Ian Pilcher [this message]
2017-12-31 8:28 ` Greg KH
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='p2bnoe$v7q$1@blaine.gmane.org' \
--to=arequipeno@gmail.com \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).