Thread (33 messages) 33 messages, 11 authors, 2018-11-26

[PATCH 3/9] drm: replace "drm_dev_unref" function with "drm_dev_put"

From: jani.nikula@linux.intel.com (Jani Nikula)
Date: 2018-11-20 09:54:15
Also in: dri-devel, linux-doc, linux-renesas-soc, lkml

On Fri, 16 Nov 2018, Fernando [off-list ref] wrote:
And, related to this, what is the "good" branch to start developing
new drm patches? Is is "drm-next" or "linux-next"? Or does it change
depending on how much time until the merge window closes?
I advise most of our developers to work on drm-tip because it contains
the latest stuff in drm core, i915, amd, most of the small drivers, as
well as sound. It's a bit like "linux-next for graphics". And you don't
really have to care about the merge cycles with that.

But YMMV, it probably doesn't work for everyone.

BR,
Jani.


-- 
Jani Nikula, Intel Open Source Graphics Center
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help