* How to report regression in stable tree?
@ 2017-12-30 19:16 Ian Pilcher
2017-12-30 22:41 ` Ben Hutchings
2017-12-31 8:28 ` Greg KH
0 siblings, 2 replies; 4+ messages in thread
From: Ian Pilcher @ 2017-12-30 19:16 UTC (permalink / raw)
To: stable
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?)
Thanks!
--
========================================================================
Ian Pilcher arequipeno@gmail.com
-------- "I grew up before Mark Zuckerberg invented friendship" --------
========================================================================
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: How to report regression in stable tree?
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
1 sibling, 1 reply; 4+ messages in thread
From: Ben Hutchings @ 2017-12-30 22:41 UTC (permalink / raw)
To: Ian Pilcher, stable
[-- Attachment #1: Type: text/plain, Size: 733 bytes --]
On Sat, 2017-12-30 at 13:16 -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?)
The kernel.org Bugzilla is only used for a few areas of mainline
development, and I would expect stable regressions in those areas to be
accepted there too.
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
Ben.
--
Ben Hutchings
The first rule of tautology club is the first rule of tautology club.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: How to report regression in stable tree?
2017-12-30 19:16 How to report regression in stable tree? Ian Pilcher
2017-12-30 22:41 ` Ben Hutchings
@ 2017-12-31 8:28 ` Greg KH
1 sibling, 0 replies; 4+ messages in thread
From: Greg KH @ 2017-12-31 8:28 UTC (permalink / raw)
To: Ian Pilcher; +Cc: stable
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: How to report regression in stable tree?
2017-12-30 22:41 ` Ben Hutchings
@ 2017-12-31 22:20 ` Ian Pilcher
0 siblings, 0 replies; 4+ messages in thread
From: Ian Pilcher @ 2017-12-31 22:20 UTC (permalink / raw)
To: stable
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" --------
========================================================================
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2017-12-31 22:21 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).