From: Jani Nikula <jani.nikula@linux.intel.com>
To: Fernando <greenfoo@gluegarage.com>,
Lucas Stach <l.stach@pengutronix.de>,
dri-devel@lists.freedesktop.org
Cc: Haneen Mohammed <hamohammed.sa@gmail.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Gilles Muller <Gilles.Muller@lip6.fr>,
David Airlie <airlied@linux.ie>,
virtualization@lists.linux-foundation.org,
Gerd Hoffmann <kraxel@redhat.com>,
cocci@systeme.lip6.fr, Marek Vasut <marex@denx.de>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, Alexey Brodkin <abrodkin@synopsys.com>,
Maxime Ripard <maxime.ripard@bootlin.com>,
Ludovic Desroches <ludovic.desroches@microchip.com>,
Russell King <linux+etnaviv@armlinux.org.uk>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Nicolas Palix <nicolas.palix@imag.fr>,
etnaviv@lists.freedesktop.org,
Julia Lawall <Julia.Lawall@lip6.fr>, Sean Paul <sean@poorly.run>,
linux-arm-kernel@lists.infradead.org,
Michal Marek <michal.lkml@markovi.net>,
Boris Brezillon <boris.brezillon@bootlin.com>,
linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>,
Shawn Guo <shawnguo@kernel.org>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>
Subject: Re: [PATCH 3/9] drm: replace "drm_dev_unref" function with "drm_dev_put"
Date: Tue, 20 Nov 2018 11:53:43 +0200 [thread overview]
Message-ID: <87lg5of520.fsf@intel.com> (raw)
In-Reply-To: <1542387884.1134874.1579436592.07F916C5@webmail.messagingengine.com>
On Fri, 16 Nov 2018, Fernando <greenfoo@gluegarage.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
WARNING: multiple messages have this Message-ID (diff)
From: jani.nikula@linux.intel.com (Jani Nikula)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/9] drm: replace "drm_dev_unref" function with "drm_dev_put"
Date: Tue, 20 Nov 2018 11:53:43 +0200 [thread overview]
Message-ID: <87lg5of520.fsf@intel.com> (raw)
In-Reply-To: <1542387884.1134874.1579436592.07F916C5@webmail.messagingengine.com>
On Fri, 16 Nov 2018, Fernando <greenfoo@gluegarage.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
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Fernando <greenfoo@gluegarage.com>,
Lucas Stach <l.stach@pengutronix.de>,
dri-devel@lists.freedesktop.org
Cc: Haneen Mohammed <hamohammed.sa@gmail.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Gilles Muller <Gilles.Muller@lip6.fr>,
David Airlie <airlied@linux.ie>,
virtualization@lists.linux-foundation.org,
Gerd Hoffmann <kraxel@redhat.com>,
cocci@systeme.lip6.fr, Marek Vasut <marex@denx.de>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, Alexey Brodkin <abrodkin@synopsys.com>,
Maxime Ripard <maxime.ripard@bootlin.com>,
Ludovic Desroches <ludovic.desroches@microchip.com>,
Russell King <linux+etnaviv@armlinux.org.uk>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Nicolas Palix <nicolas.palix@imag.fr>,
etnaviv@lists.freedesktop.org,
Julia Lawall <Julia.Lawall@lip6.fr>, Sean Paul <sean@poorly.run>,
linux-arm-kernel@lists.infradead.org, Michal
Subject: Re: [PATCH 3/9] drm: replace "drm_dev_unref" function with "drm_dev_put"
Date: Tue, 20 Nov 2018 11:53:43 +0200 [thread overview]
Message-ID: <87lg5of520.fsf@intel.com> (raw)
In-Reply-To: <1542387884.1134874.1579436592.07F916C5@webmail.messagingengine.com>
On Fri, 16 Nov 2018, Fernando <greenfoo@gluegarage.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
next prev parent reply other threads:[~2018-11-20 9:53 UTC|newest]
Thread overview: 116+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 22:16 [PATCH 0/9] drm: remove deprecated functions Fernando Ramos
2018-11-15 22:16 ` Fernando Ramos
2018-11-15 22:16 ` Fernando Ramos
2018-11-15 22:16 ` [PATCH 1/9] drm: replace "drm_gem_object_unreference_unlocked" function with "*put_unlocked" Fernando Ramos
2018-11-15 22:16 ` Fernando Ramos
2018-11-15 22:16 ` Fernando Ramos
2018-11-24 20:38 ` Linus Walleij
2018-11-24 20:38 ` Linus Walleij
2018-11-24 20:38 ` Linus Walleij
2018-11-15 22:16 ` [PATCH 2/9] drm: remove deprecated "[__]drm_gem_object_[un]reference[_locked]" functions Fernando Ramos
2018-11-15 22:16 ` Fernando Ramos
2018-11-15 22:16 ` Fernando Ramos
2018-11-24 20:38 ` Linus Walleij
2018-11-24 20:38 ` Linus Walleij
2018-11-24 20:38 ` Linus Walleij
2018-11-15 22:16 ` [PATCH 3/9] drm: replace "drm_dev_unref" function with "drm_dev_put" Fernando Ramos
2018-11-15 22:16 ` Fernando Ramos
2018-11-15 22:16 ` Fernando Ramos
2018-11-15 23:00 ` Boris Brezillon
2018-11-15 23:00 ` Boris Brezillon
2018-11-15 23:00 ` Boris Brezillon
2018-11-16 10:15 ` Lucas Stach
2018-11-16 10:15 ` Lucas Stach
2018-11-16 10:15 ` Lucas Stach
2018-11-16 17:04 ` Fernando
2018-11-16 17:04 ` Fernando
2018-11-16 17:04 ` Fernando
2018-11-20 9:53 ` Jani Nikula [this message]
2018-11-20 9:53 ` Jani Nikula
2018-11-20 9:53 ` Jani Nikula
2018-11-20 9:53 ` Jani Nikula
2018-11-24 20:44 ` Linus Walleij
2018-11-24 20:44 ` Linus Walleij
2018-11-24 20:44 ` Linus Walleij
2018-11-16 11:41 ` Alexey Brodkin
2018-11-16 11:41 ` Alexey Brodkin
2018-11-16 11:41 ` Alexey Brodkin
2018-11-19 11:39 ` Stefan Agner
2018-11-19 11:39 ` Stefan Agner
2018-11-19 11:39 ` Stefan Agner
2018-11-19 12:13 ` Shawn Guo
2018-11-19 12:13 ` Shawn Guo
2018-11-19 12:13 ` Shawn Guo
2018-11-19 12:13 ` Shawn Guo
2018-11-24 20:44 ` Linus Walleij
2018-11-24 20:44 ` Linus Walleij
2018-11-24 20:44 ` Linus Walleij
2018-11-15 22:16 ` [PATCH 4/9] drm: remove deprecated "drm_dev_unref" function Fernando Ramos
2018-11-15 22:16 ` Fernando Ramos
2018-11-15 22:16 ` Fernando Ramos
2018-11-24 20:45 ` Linus Walleij
2018-11-24 20:45 ` Linus Walleij
2018-11-24 20:45 ` Linus Walleij
2018-11-15 22:16 ` [PATCH 5/9] drm: replace "drm_connector_unreference" with "drm_connector_put" Fernando Ramos
2018-11-15 22:16 ` Fernando Ramos
2018-11-15 22:16 ` Fernando Ramos
2018-11-24 20:47 ` Linus Walleij
2018-11-24 20:47 ` Linus Walleij
2018-11-24 20:47 ` Linus Walleij
2018-11-15 22:16 ` [PATCH 6/9] drm: remove deprecated "drm_connector_[un]reference" functions Fernando Ramos
2018-11-15 22:16 ` Fernando Ramos
2018-11-15 22:16 ` Fernando Ramos
2018-11-21 18:56 ` Lyude Paul
2018-11-21 18:56 ` Lyude Paul
2018-11-21 18:56 ` Lyude Paul
2018-11-24 20:49 ` Linus Walleij
2018-11-24 20:49 ` Linus Walleij
2018-11-24 20:49 ` Linus Walleij
2018-11-15 22:16 ` [PATCH 7/9] drm: remove deprecated "drm_framebuffer_[un]reference" functions Fernando Ramos
2018-11-15 22:16 ` Fernando Ramos
2018-11-15 22:16 ` Fernando Ramos
2018-11-24 20:55 ` Linus Walleij
2018-11-24 20:55 ` Linus Walleij
2018-11-24 20:55 ` Linus Walleij
2018-11-15 22:16 ` [PATCH 8/9] drm: remove no longer needed drm-get-put coccinelle script Fernando Ramos
2018-11-15 22:16 ` Fernando Ramos
2018-11-15 22:16 ` Fernando Ramos
2018-11-18 11:04 ` Julia Lawall
2018-11-18 11:04 ` Julia Lawall
2018-11-18 11:04 ` Julia Lawall
2018-11-18 11:04 ` Julia Lawall
2018-11-24 20:58 ` Linus Walleij
2018-11-24 20:58 ` Linus Walleij
2018-11-24 20:58 ` Linus Walleij
2018-11-15 22:16 ` [PATCH 9/9] docs: drm: remove no longer relevant TODO entry Fernando Ramos
2018-11-15 22:16 ` Fernando Ramos
2018-11-15 22:16 ` Fernando Ramos
2018-11-24 20:59 ` Linus Walleij
2018-11-24 20:59 ` Linus Walleij
2018-11-24 20:59 ` Linus Walleij
2018-11-15 22:38 ` [PATCH 0/9] drm: remove deprecated functions Linus Walleij
2018-11-15 22:38 ` Linus Walleij
2018-11-15 22:38 ` Linus Walleij
2018-11-21 9:42 ` Daniel Vetter
2018-11-21 9:42 ` Daniel Vetter
2018-11-21 9:42 ` Daniel Vetter
2018-11-21 18:21 ` Laurent Pinchart
2018-11-22 8:55 ` Daniel Vetter
2018-11-22 8:55 ` Daniel Vetter
2018-11-22 8:55 ` Daniel Vetter
2018-11-22 8:55 ` Daniel Vetter
2018-11-21 18:21 ` Laurent Pinchart
2018-11-24 21:17 ` Linus Walleij
2018-11-24 21:17 ` Linus Walleij
2018-11-24 21:17 ` Linus Walleij
2018-11-26 14:12 ` Daniel Vetter
2018-11-26 14:12 ` Daniel Vetter
2018-11-26 14:12 ` Daniel Vetter
2018-11-26 14:12 ` Daniel Vetter
2018-11-29 14:45 ` Linus Walleij
2018-11-29 14:45 ` Linus Walleij
2018-11-29 14:55 ` Daniel Vetter
2018-11-29 14:55 ` Daniel Vetter
2018-11-29 14:55 ` Daniel Vetter
2018-11-29 14:55 ` Daniel Vetter
2018-11-21 9:42 ` Daniel Vetter
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=87lg5of520.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=Gilles.Muller@lip6.fr \
--cc=Julia.Lawall@lip6.fr \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=abrodkin@synopsys.com \
--cc=airlied@linux.ie \
--cc=alexandre.belloni@bootlin.com \
--cc=boris.brezillon@bootlin.com \
--cc=cocci@systeme.lip6.fr \
--cc=corbet@lwn.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=etnaviv@lists.freedesktop.org \
--cc=greenfoo@gluegarage.com \
--cc=hamohammed.sa@gmail.com \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=kraxel@redhat.com \
--cc=l.stach@pengutronix.de \
--cc=linux+etnaviv@armlinux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=marex@denx.de \
--cc=maxime.ripard@bootlin.com \
--cc=michal.lkml@markovi.net \
--cc=nicolas.ferre@microchip.com \
--cc=nicolas.palix@imag.fr \
--cc=sean@poorly.run \
--cc=shawnguo@kernel.org \
--cc=virtualization@lists.linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.