public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Lionel Landwerlin <lionel.g.landwerlin@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 20:50:53 -0400	[thread overview]
Message-ID: <abNfbWemfOKGNrVZ@intel.com> (raw)
In-Reply-To: <b7f67081-7b8f-48e0-8f9e-bcbad47165d6@sirena.org.uk>

On Thu, Mar 12, 2026 at 11:43:40AM +0000, Mark Brown wrote:
> 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.

We can work with topic branch as well, but the backmerge is not a hard process
for us. We should just not have rushed with this patch to start with, then
we could had put the branch in sync.

My apologies for not identifying earlier that this was the case here when I
first tried to apply the patch. I wrongly assumed the patch was not based
on the right branch...

The pull-requests are already happening, so we should be back in sync soon,
then you can re-enable the branch.

Sorry,
Rodrigo.





  reply	other threads:[~2026-03-13  0:51 UTC|newest]

Thread overview: 25+ 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
2026-03-13  0:50             ` Rodrigo Vivi [this message]
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 --
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=abNfbWemfOKGNrVZ@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=broonie@kernel.org \
    --cc=jani.nikula@intel.com \
    --cc=jose.souza@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=lionel.g.landwerlin@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