Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: "Lin, Shuicheng" <shuicheng.lin@intel.com>
Cc: "Brost, Matthew" <matthew.brost@intel.com>,
	"Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: FAILED: patch "[PATCH] drm/xe/sync: Cleanup partially initialized sync on parse" failed to apply to 6.12-stable tree
Date: Wed, 18 Mar 2026 13:25:01 +0100	[thread overview]
Message-ID: <2026031851-glamour-unusual-8513@gregkh> (raw)
In-Reply-To: <DM4PR11MB5456067D5FE7F51042296C41EA41A@DM4PR11MB5456.namprd11.prod.outlook.com>

On Tue, Mar 17, 2026 at 05:10:53PM +0000, Lin, Shuicheng wrote:
> On Tue, Mar 17, 2026 9:32 AM greg k-h wrote:
> > On Tue, Mar 17, 2026 at 04:27:46PM +0000, Lin, Shuicheng wrote:
> > > On Tue, Mar 17, 2026 4:48 AM gregkh wrote:
> > > > The patch below does not apply to the 6.12-stable tree.
> > > > If someone wants it applied there, or to any other stable or
> > > > longterm tree, then please email the backport, including the
> > > > original git commit id to <stable@vger.kernel.org>.
> > > >
> > > > To reproduce the conflict and resubmit, you may use the following
> > commands:
> > > >
> > > > git fetch
> > > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/
> > > > linux-6.12.y git checkout FETCH_HEAD git cherry-pick -x
> > > > 1bfd7575092420ba5a0b944953c95b74a5646ff8
> > > > # <resolve conflicts, build, test, etc.> git commit -s git
> > > > send-email --to '<stable@vger.kernel.org>' --in-reply-to
> > > > '2026031732-size-unfasten- 2bf3@gregkh' --subject-prefix 'PATCH 6.12.y'
> > HEAD^..
> > >
> > > I cannot reproduce the failure with upper cmd.
> > > The patch could be applied successfully without conflict.
> > > Anyway, I follow the instructions re-send the patch.
> > > Let me know if it still has issue.
> > 
> > Try building it after it is applied and notice how it breaks the build :(
> 
> I tried to do it, and it could build successfully.
> I checked the code and cannot find what will cause the build failure.
> Could you please share me the failure signature?

  CC [M]  drivers/gpu/drm/xe/xe_sync.o
drivers/gpu/drm/xe/xe_sync.c: In function ‘xe_sync_entry_parse’:
drivers/gpu/drm/xe/xe_sync.c:182:33: error: label ‘free_sync’ used but not defined
  182 |                                 goto free_sync;
      |                                 ^~~~
drivers/gpu/drm/xe/xe_sync.c: In function ‘xe_sync_entry_add_deps’:
drivers/gpu/drm/xe/xe_sync.c:228:16: error: ‘err’ undeclared (first use in this function)
  228 |         return err;
      |                ^~~
drivers/gpu/drm/xe/xe_sync.c:228:16: note: each undeclared identifier is reported only once for each function it appears in
drivers/gpu/drm/xe/xe_sync.c:226:1: error: label ‘free_sync’ defined but not used [-Werror=unused-label]
  226 | free_sync:
      | ^~~~~~~~~
cc1: all warnings being treated as errors



  reply	other threads:[~2026-03-18 12:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-17 11:47 FAILED: patch "[PATCH] drm/xe/sync: Cleanup partially initialized sync on parse" failed to apply to 6.12-stable tree gregkh
2026-03-17 16:22 ` [PATCH 6.12.y] drm/xe/sync: Cleanup partially initialized sync on parse failure Shuicheng Lin
2026-03-17 16:27 ` FAILED: patch "[PATCH] drm/xe/sync: Cleanup partially initialized sync on parse" failed to apply to 6.12-stable tree Lin, Shuicheng
2026-03-17 16:31   ` gregkh
2026-03-17 17:10     ` Lin, Shuicheng
2026-03-18 12:25       ` gregkh [this message]
2026-03-18 16:26         ` Lin, Shuicheng
2026-03-18 16:58           ` gregkh
2026-03-18 17:20             ` Lin, Shuicheng
2026-03-19  9:48               ` gregkh

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=2026031851-glamour-unusual-8513@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=matthew.brost@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=shuicheng.lin@intel.com \
    --cc=stable@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox