linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: "Nikula, Jani" <jani.nikula@linux.intel.com>,
	Daniel Vetter <daniel@ffwll.ch>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: Dave Airlie <airlied@linux.ie>,
	DRI <dri-devel@lists.freedesktop.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: linux-next: build warning after merge of the drm tree
Date: Wed, 27 Oct 2021 15:12:44 +0300	[thread overview]
Message-ID: <163533676481.68716.4009950051571709814@jlahtine-mobl.ger.corp.intel.com> (raw)
In-Reply-To: <CAKMK7uFWFVC0be2foiP8+2=vrqyh1e4mqkuk+2xY+fgSWAExyQ@mail.gmail.com>

(+ Tvrtko who was recently added as a drm/i915 co-maintainer)

Quoting Daniel Vetter (2021-01-22 10:40:48)
> On Fri, Jan 22, 2021 at 8:29 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > Hi Daniel,
> >
> > On Fri, 22 Jan 2021 08:17:58 +0100 Daniel Vetter <daniel@ffwll.ch> wrote:
> > >
> > > Hm that has been in drm-intel-gt-next for a few days, is that tree not
> > > in linux-next?
> >
> > It is not.

Hi Stephen,

We should be now good to go and add drm-intel-gt-next to linux-next.

The branch would be as follows:

drm-intel-gt-next	git://anongit.freedesktop.org/drm-intel	for-linux-next-gt

Notice the "-gt" and the end of the for-linux-next branch name. This should eliminate
the gap we have been having. The change to add it to the DIM tool is here:

https://gitlab.freedesktop.org/drm/maintainer-tools/-/commit/7b5c2c29cdbc054e8c8fce38f095c56290fc4833

So once all developers have updated their tooling (for which they will
get an automatic nag message) we should be all up-to-date for future
merge windows.

Regards, Joonas

> Adding -intel maintainers to get that sorted.
> -Daniel
> 
> > These are the drm branches currently in linux-next:
> 
> Oh for ordering maybe put drm-misc ahead of the other subtrees, -misc
> is where nowadays a lot of refactorings and core changes land.
> Probably doesn't matter in practice.
> -Daniel
> 
> > drm-fixes       git://git.freedesktop.org/git/drm/drm.git       drm-fixes
> > amdgpu-fixes    git://people.freedesktop.org/~agd5f/linux       drm-fixes
> > drm-intel-fixes git://anongit.freedesktop.org/drm-intel         for-linux-next-fixes
> > drm-misc-fixes  git://anongit.freedesktop.org/drm/drm-misc      for-linux-next-fixes
> > drm             git://git.freedesktop.org/git/drm/drm.git       drm-next
> > amdgpu          https://gitlab.freedesktop.org/agd5f/linux      drm-next
> > drm-intel       git://anongit.freedesktop.org/drm-intel         for-linux-next
> > drm-tegra       git://anongit.freedesktop.org/tegra/linux.git   drm/tegra/for-next
> > drm-misc        git://anongit.freedesktop.org/drm/drm-misc      for-linux-next
> > drm-msm         https://gitlab.freedesktop.org/drm/msm.git      msm-next
> > imx-drm         https://git.pengutronix.de/git/pza/linux        imx-drm/next
> > etnaviv         https://git.pengutronix.de/git/lst/linux        etnaviv/next
> >
> > --
> > Cheers,
> > Stephen Rothwell
> 
> 
> 
> -- 
> Daniel Vetter
> Software Engineer, Intel Corporation
> http://blog.ffwll.ch

  reply	other threads:[~2021-10-27 12:12 UTC|newest]

Thread overview: 79+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-22  0:59 linux-next: build warning after merge of the drm tree Stephen Rothwell
2021-01-22  7:17 ` Daniel Vetter
2021-01-22  7:29   ` Stephen Rothwell
2021-01-22  8:40     ` Daniel Vetter
2021-10-27 12:12       ` Joonas Lahtinen [this message]
2021-10-27 20:51         ` Stephen Rothwell
2021-10-28  9:16           ` Joonas Lahtinen
2021-02-01  1:55 ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2024-02-07  6:17 Stephen Rothwell
2024-02-07 14:19 ` Rodrigo Vivi
2024-01-05  6:47 Stephen Rothwell
2024-01-25  0:33 ` Stephen Rothwell
2024-01-26  8:48   ` Thomas Hellström
2024-01-02  0:12 Stephen Rothwell
2024-01-03  1:19 ` Stephen Rothwell
2024-01-03  1:27   ` Stephen Rothwell
2024-01-04 16:52     ` Jani Nikula
2023-11-24  2:25 Stephen Rothwell
2023-11-24 12:35 ` Donald Robson
2023-11-24  2:23 Stephen Rothwell
2023-11-24  2:17 Stephen Rothwell
2023-04-11  6:02 Stephen Rothwell
2023-04-11  9:48 ` Andi Shyti
2023-04-11  6:01 Stephen Rothwell
2023-03-30  3:28 Stephen Rothwell
2023-03-30 14:28 ` Rob Clark
2023-07-11 23:17   ` Stephen Rothwell
2023-07-24  3:50     ` Stephen Rothwell
2023-02-03  2:46 Stephen Rothwell
2023-02-03 12:32 ` Gustavo Sousa
2023-01-05  3:43 Stephen Rothwell
2023-01-05  3:21 Stephen Rothwell
2023-01-05  3:17 Stephen Rothwell
2022-11-07  3:29 Stephen Rothwell
2022-11-07 20:31 ` John Harrison
2022-02-02  4:10 Stephen Rothwell
2022-03-02  1:32 ` Stephen Rothwell
2022-02-02  4:02 Stephen Rothwell
2022-02-02  4:03 ` Stephen Rothwell
2022-02-02  8:38   ` Hans de Goede
2022-02-04 19:29     ` Rajat Jain
2022-03-02  1:34     ` Stephen Rothwell
2022-03-02 10:32       ` Hans de Goede
2022-03-02 11:38         ` Stephen Rothwell
2021-04-01  7:19 Stephen Rothwell
2021-04-21  6:28 ` Stephen Rothwell
2021-03-17  7:42 Stephen Rothwell
2021-03-17  2:53 Stephen Rothwell
2020-11-05  7:02 Stephen Rothwell
2020-11-16  0:01 ` Stephen Rothwell
2020-09-23  3:36 Stephen Rothwell
2020-09-23  6:27 ` Tomi Valkeinen
2020-10-01  9:47 ` Stephen Rothwell
2020-05-11  3:47 Stephen Rothwell
2020-05-11  4:04 ` Randy Dunlap
2019-02-01  0:53 Stephen Rothwell
2018-06-25  4:22 Stephen Rothwell
2018-06-25  4:22 ` Stephen Rothwell
2018-02-18 23:18 Stephen Rothwell
2018-03-02  1:49 ` Stephen Rothwell
2017-12-04  0:30 Stephen Rothwell
2017-12-04  0:57 ` Dave Airlie
2017-06-19  1:40 Stephen Rothwell
2017-05-19  2:10 Stephen Rothwell
2017-05-03 22:33 Stephen Rothwell
     [not found] ` <tencent_62AF37B85899E2EA593CCE3B@qq.com>
2017-05-04  1:42   ` Stephen Rothwell
2015-06-04 12:31 Stephen Rothwell
2015-05-20  6:54 Stephen Rothwell
2015-05-20 11:49 ` Sergey Senozhatsky
2015-05-20  6:31 Stephen Rothwell
2015-05-20 19:51 ` Russell King - ARM Linux
2013-06-28  3:30 Stephen Rothwell
2013-06-28  3:33 ` Dave Airlie
2013-04-19  5:50 Stephen Rothwell
2012-05-08  5:08 Stephen Rothwell
2011-11-28  2:41 Stephen Rothwell
2011-11-28  2:36 Stephen Rothwell
2011-05-12  2:14 Stephen Rothwell
2010-03-01  7:14 Stephen Rothwell

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=163533676481.68716.4009950051571709814@jlahtine-mobl.ger.corp.intel.com \
    --to=joonas.lahtinen@linux.intel.com \
    --cc=airlied@linux.ie \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rodrigo.vivi@intel.com \
    --cc=sfr@canb.auug.org.au \
    --cc=tvrtko.ursulin@linux.intel.com \
    /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 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).