public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Maciej Wieczor-Retman <maciej.wieczor-retman@intel.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the mm-hotfixes tree
Date: Mon, 8 Dec 2025 17:37:29 -0800	[thread overview]
Message-ID: <20251208173729.b553b48c88d17954e1efd671@linux-foundation.org> (raw)
In-Reply-To: <ja5zht46osfzx7fowemw3v6ucnrugzpnhbf5l5ta7xxuywry6i@3trcfqmhk2ec>

On Mon, 8 Dec 2025 11:30:16 +0100 Maciej Wieczor-Retman <maciej.wieczor-retman@intel.com> wrote:

> This flag, KASAN_VMALLOC_KEEP_TAG was defined in the first patch by Jiayuan in
> my three piece series [1]. I looked over git logs in mm-unstable and
> mm-hotfixes-unstable and I guess it wasn't pulled there but my two following
> patches were.
> 
> Could you pull the [1] missing patch Andrew? I think that should fix this issue.
> Thanks :)
> 
> [1] https://lore.kernel.org/all/247fd641cbf4a8e6c8135051772867f6bd2610ad.1764945396.git.m.wieczorretman@pm.me/

thanks, yup, restored.

  reply	other threads:[~2025-12-09  1:37 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-07 21:35 linux-next: build failure after merge of the mm-hotfixes tree Stephen Rothwell
2025-12-08 10:30 ` Maciej Wieczor-Retman
2025-12-09  1:37   ` Andrew Morton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-08-21  6:05 Stephen Rothwell
2025-08-21  9:49 ` Harry Yoo
2025-05-28 23:59 Stephen Rothwell
2025-05-29  0:02 ` Andrew Morton
2025-05-29  1:57   ` Stephen Rothwell
2025-05-29  0:03 ` Stephen Rothwell
2024-07-01  0:16 Stephen Rothwell
2024-07-01  1:01 ` Stephen Rothwell
2024-07-01 18:15   ` Yang Shi
2024-07-02 22:44     ` Stephen Rothwell
2024-07-02 23:22       ` Stephen Rothwell
2024-07-03  0:40         ` Yang Shi
2023-12-13 22:18 Stephen Rothwell
2023-12-13 23:31 ` Liam R. Howlett
2022-12-12 22:30 Stephen Rothwell
2022-12-13  1:34 ` Kefeng Wang
2022-12-13  2:23   ` Andrew Morton
2022-12-13  2:45     ` Stephen Rothwell
2022-12-13  2:54     ` Kefeng Wang
2022-11-25  1:10 Stephen Rothwell
2022-11-25  5:24 ` Juergen Gross
2022-11-25  5:24 ` Andrew Morton
2022-11-25  5:48   ` 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=20251208173729.b553b48c88d17954e1efd671@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=maciej.wieczor-retman@intel.com \
    --cc=sfr@canb.auug.org.au \
    /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