Re: Sphinx builds always write to the source directory

;t know how to tell Sphinx to find them there. > > Are these issues likely to be fixed? > > Ben. -- Jani Nikula, Intel Open Source Technology Center

[PATCH RESEND] Documentation/sphinx: prevent generation of .pyc files in the source tree

/camuhmdvxqph7-9xj+ye_pgoa+-fe0969cskoehyh3uubycr...@mail.gmail.com Reported-by: Geert Uytterhoeven References: http://lkml.kernel.org/r/1485816692.2900.17.ca...@decadent.org.uk Reported-by: Ben Hutchings Cc: Jonathan Corbet Signed-off-by: Jani Nikula --- Documentation/Makefile.sphinx | 1 + 1 file

Re: [PATCH RESEND] Documentation/sphinx: prevent generation of .pyc files in the source tree

On Wed, 01 Feb 2017, Jonathan Corbet wrote: > On Tue, 31 Jan 2017 20:18:05 +0200 > Jani Nikula wrote: > >> Considering the small amount of python code to compile (assuming sphinx >> itself has .pyc around), the impact on build is neglible. > > Hey...don't you

Bug#1075770: [bug report] adlp_tc_phy_connect [i915] floods logs with drm_WARN_ON(tc->mode == TC_PORT_LEGACY) call traces

; on replies, so that the interested parties (including me!) are kept > in the loop. > Thanks a lot for your time and for any help you may provide! Please file i915 bugs at fdo gitlab as described at [1]. BR, Jani. [1] https://drm.pages.freedesktop.org/intel-docs/how-to-file-i915-bugs.html -- Jani Nikula, Intel

Bug#1075770: [bug report] adlp_tc_phy_connect [i915] floods logs with drm_WARN_ON(tc->mode == TC_PORT_LEGACY) call traces

logs. It's easier to label and reference issues on a bug tracker. It's easier (yes, for us) to manage the issues, and the people working on them, on a bug tracker. And so on. BR, Jani. -- Jani Nikula, Intel

Bug#971068: Assertion failure in i915 intel_display.c#assert_plane() after resume from hibernation

if the proper fixes have been backported to v6.1 stable kernels. BR, Jani. -- Jani Nikula, Intel Open Source Graphics Center