lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87lg5of520.fsf@intel.com>
Date:   Tue, 20 Nov 2018 11:53:43 +0200
From:   Jani Nikula <jani.nikula@...ux.intel.com>
To:     Fernando <greenfoo@...egarage.com>,
        Lucas Stach <l.stach@...gutronix.de>,
        dri-devel@...ts.freedesktop.org
Cc:     Haneen Mohammed <hamohammed.sa@...il.com>,
        Alexandre Belloni <alexandre.belloni@...tlin.com>,
        Gilles Muller <Gilles.Muller@...6.fr>,
        David Airlie <airlied@...ux.ie>,
        virtualization@...ts.linux-foundation.org,
        Gerd Hoffmann <kraxel@...hat.com>, cocci@...teme.lip6.fr,
        Marek Vasut <marex@...x.de>, Jonathan Corbet <corbet@....net>,
        linux-doc@...r.kernel.org, Alexey Brodkin <abrodkin@...opsys.com>,
        Maxime Ripard <maxime.ripard@...tlin.com>,
        Ludovic Desroches <ludovic.desroches@...rochip.com>,
        Russell King <linux+etnaviv@...linux.org.uk>,
        Nicolas Ferre <nicolas.ferre@...rochip.com>,
        Nicolas Palix <nicolas.palix@...g.fr>,
        etnaviv@...ts.freedesktop.org, Julia Lawall <Julia.Lawall@...6.fr>,
        Sean Paul <sean@...rly.run>,
        linux-arm-kernel@...ts.infradead.org,
        Michal Marek <michal.lkml@...kovi.net>,
        Boris Brezillon <boris.brezillon@...tlin.com>,
        linux-kernel@...r.kernel.org, linux-renesas-soc@...r.kernel.org,
        Kieran Bingham <kieran.bingham+renesas@...asonboard.com>,
        Shawn Guo <shawnguo@...nel.org>,
        Laurent Pinchart <Laurent.pinchart@...asonboard.com>
Subject: Re: [PATCH 3/9] drm: replace "drm_dev_unref" function with "drm_dev_put"

On Fri, 16 Nov 2018, Fernando <greenfoo@...egarage.com> 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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ