Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, teddy.astie@vates.tech
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: =?utf-8?Q?[PATCH=205.15.y]=20xen:=20replace=20xen=5Fremap()=20with=20memremap()?=
Date: Thu,  3 Jul 2025 14:34:55 -0400	[thread overview]
Message-ID: <20250703095236-eaaec1094f6ebb20@stable.kernel.org> (raw)
In-Reply-To: <2398723b73ddd9923a9bb994364c2c7d3b89d21d.1751446695.git.teddy.astie@vates.tech>

[ Sasha's backport helper bot ]

Hi,

Summary of potential issues:
❌ Build failures detected

The upstream commit SHA1 provided is correct: 41925b105e345ebc84cedb64f59d20cb14a62613

WARNING: Author mismatch between patch and upstream commit:
Backport author: "Teddy Astie"<teddy.astie@vates.tech>
Commit author: Juergen Gross<jgross@suse.com>

Note: The patch differs from the upstream commit:
---
1:  41925b105e345 < -:  ------------- xen: replace xen_remap() with memremap()
-:  ------------- > 1:  e60eb441596d1 Linux 6.15.4
---

Results of testing on various branches:

| Branch                    | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.15.y       |  Success    |  Success   |
| stable/linux-6.12.y       |  Success    |  Success   |
| stable/linux-6.6.y        |  Success    |  Success   |
| stable/linux-6.1.y        |  Success    |  Success   |
| stable/linux-5.15.y       |  Success    |  Failed    |
| stable/linux-5.10.y       |  Success    |  Success   |
| stable/linux-5.4.y        |  Success    |  Success   |

Build Errors:
Build error for stable/linux-5.15.y:
    Building current HEAD with log output
    To ssh://sws/home/sasha/linux
     * [new branch]                  HEAD -> log-branch-ec112106cafa
    drivers/tty/hvc/hvc_xen.c: In function 'xen_hvm_console_init':
    drivers/tty/hvc/hvc_xen.c:273:22: error: implicit declaration of function 'xen_remap'; did you mean 'memremap'? [-Werror=implicit-function-declaration]
      273 |         info->intf = xen_remap(gfn << XEN_PAGE_SHIFT, XEN_PAGE_SIZE);
          |                      ^~~~~~~~~
          |                      memremap
    drivers/tty/hvc/hvc_xen.c:273:20: warning: assignment to 'struct xencons_interface *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
      273 |         info->intf = xen_remap(gfn << XEN_PAGE_SHIFT, XEN_PAGE_SIZE);
          |                    ^
    cc1: some warnings being treated as errors
    make[3]: *** [scripts/Makefile.build:289: drivers/tty/hvc/hvc_xen.o] Error 1
    make[3]: Target '__build' not remade because of errors.
    make[2]: *** [scripts/Makefile.build:552: drivers/tty/hvc] Error 2
    make[2]: Target '__build' not remade because of errors.
    make[1]: *** [scripts/Makefile.build:552: drivers/tty] Error 2
    make[1]: Target '__build' not remade because of errors.
    make: *** [Makefile:1926: drivers] Error 2
    make: Target '__all' not remade because of errors.
    Build x86: exited with code 2
    Cleaning up worktrees...
    Cleaning up worktrees...

      reply	other threads:[~2025-07-03 18:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-02  9:14 [PATCH 5.15.y] xen: replace xen_remap() with memremap() Teddy Astie
2025-07-03 18:34 ` Sasha Levin [this message]

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=20250703095236-eaaec1094f6ebb20@stable.kernel.org \
    --to=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=teddy.astie@vates.tech \
    /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