From: Greg KH <gregkh@linuxfoundation.org>
To: Ian Pilcher <arequipeno@gmail.com>
Cc: stable@vger.kernel.org
Subject: Re: How to report regression in stable tree?
Date: Sun, 31 Dec 2017 09:28:12 +0100 [thread overview]
Message-ID: <20171231082812.GD25965@kroah.com> (raw)
In-Reply-To: <p28oid$4dp$1@blaine.gmane.org>
On Sat, Dec 30, 2017 at 01:16:24PM -0600, Ian Pilcher wrote:
> I just discovered that commit 7042c2b9a19e74972f5783ab3b7ef98ebdee293f
> in 4.14.4 completely breaks the external displays attached to my Dell
> TB16 dock.
>
> How/where should I report this? (Does the stable tree use the regular
> kernel Bugzilla?)
What Ben said was good, also you can just cc: the people on the patch
itself, and the mailing list for the subsystem, and that usually will
work (along with the stable mailing list).
thanks,
greg k-h
prev parent reply other threads:[~2017-12-31 8:28 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
2017-12-31 8:28 ` Greg KH [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=20171231082812.GD25965@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=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).