From: Mark Brown <broonie@kernel•org>
To: Lionel Landwerlin <lionel.g.landwerlin@intel•com>
Cc: Rodrigo Vivi <rodrigo.vivi@intel•com>,
"Souza, Jose" <jose.souza@intel•com>,
"linux-next@vger•kernel.org" <linux-next@vger•kernel.org>,
"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>,
"Nikula, Jani" <jani.nikula@intel•com>
Subject: Re: linux-next: build failure after merge of the drm-xe tree
Date: Thu, 12 Mar 2026 11:43:40 +0000 [thread overview]
Message-ID: <b7f67081-7b8f-48e0-8f9e-bcbad47165d6@sirena.org.uk> (raw)
In-Reply-To: <7df1c2dd-1e62-4cc6-9fb8-9f4ac160077f@intel.com>
[-- Attachment #1: Type: text/plain, Size: 702 bytes --]
On Thu, Mar 12, 2026 at 09:47:26AM +0200, Lionel Landwerlin wrote:
> On 11/03/2026 22:11, Rodrigo Vivi wrote:
> > We are in -rc3. Jani might be sending a PR in 2 weeks from now.
> > So, we might be in sync in 3 weeks. Worst case 30 days.
> > But it can be speed up with the help of the maintainers I mentioned.
> > Lionel, what do you think?
> Is there no process to deal with kind of merge issues quickly?
> If someone comes along and changes the bitmask macros again, do we have to
> wait another month after that?
The usual thing that normal trees would do would be to make a shared
branch with just the API change in it that all the affected trees could
merge and base their ongoing work off.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-03-12 11:43 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 13:08 linux-next: build failure after merge of the drm-xe tree Mark Brown
2026-03-11 17:16 ` Souza, Jose
2026-03-11 18:10 ` Rodrigo Vivi
2026-03-11 18:16 ` Souza, Jose
2026-03-11 20:11 ` Rodrigo Vivi
2026-03-12 7:47 ` Lionel Landwerlin
2026-03-12 11:43 ` Mark Brown [this message]
2026-03-13 0:50 ` Rodrigo Vivi
2026-03-13 1:18 ` Souza, Jose
2026-03-13 13:25 ` Mark Brown
2026-03-13 0:46 ` Rodrigo Vivi
2026-03-13 13:57 ` Jani Nikula
2026-03-16 17:38 ` Mark Brown
2026-03-19 8:59 ` Jani Nikula
2026-03-19 9:00 ` Jani Nikula
-- strict thread matches above, loose matches on Subject: below --
2026-06-03 14:02 Mark Brown
2026-06-04 14:35 ` Mark Brown
2026-06-04 14:43 ` Thomas Hellström
2026-06-04 14:50 ` Mark Brown
2025-03-07 2:21 Stephen Rothwell
2025-03-11 2:15 ` Stephen Rothwell
2025-03-07 1:58 Stephen Rothwell
2025-03-11 2:13 ` Stephen Rothwell
2024-12-04 13:36 Mark Brown
2024-12-04 13:46 ` Jani Nikula
2024-12-04 14:18 ` Mark Brown
2024-10-01 1:38 Stephen Rothwell
2024-02-22 8:04 Stephen Rothwell
2024-02-22 17:09 ` Lucas De Marchi
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=b7f67081-7b8f-48e0-8f9e-bcbad47165d6@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=jani.nikula@intel$(echo .)com \
--cc=jose.souza@intel$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=lionel.g.landwerlin@intel$(echo .)com \
--cc=rodrigo.vivi@intel$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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