Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Li <philip.li@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kernel test robot <lkp@intel.com>,
	David Hildenbrand <david@kernel.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	<mm-commits@vger.kernel.org>
Subject: Re: [akpm-mm:mm-new] BUILD REGRESSION dba8aba0a9a00ff781c03d82ae534fc6f8c2e263
Date: Fri, 6 Nov 2026 11:56:15 +0800	[thread overview]
Message-ID: <au1P3+HYvy4uiJMQ@rli9-mobl> (raw)
In-Reply-To: <20261105190559.5656444f0cb52cbf888427a6@linux-foundation.org>

On Thu, Nov 05, 2026 at 07:05:59PM -0800, Andrew Morton wrote:
> On Fri, 06 Nov 2026 09:53:40 +0800 kernel test robot <lkp@intel.com> wrote:
> 
> > tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-new
> > branch HEAD: dba8aba0a9a00ff781c03d82ae534fc6f8c2e263  riscv: mm: fix concurrency in mark_new_valid_map()
> > 
> > Error/Warning ids grouped by kconfigs:
> > 
> > recent_errors
> > `-- csky-allmodconfig
> >     `-- drivers-net-wireless-ath-ath11k-dbring.c:internal-compiler-error:in-final_scan_insn_1-at-final.cc
> > 
> 
> Thanks.
> 
> Am I being dumb here.  I can't find any error report other than this.

Sorry, kindly ignore this issue, it is "internal compiler error", thus there's no
public report for this. And I will config bot to avoid including such compiler issue
in the status report, that also wrongly judges the status as regression.

> 
> And I'm not going to lose much sleep about a CSKY gcc ICE in ath11k ;)
> 


      reply	other threads:[~2026-11-06  3:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-06  1:53 [akpm-mm:mm-new] BUILD REGRESSION dba8aba0a9a00ff781c03d82ae534fc6f8c2e263 kernel test robot
2026-11-06  3:05 ` Andrew Morton
2026-11-06  3:56   ` Philip Li [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=au1P3+HYvy4uiJMQ@rli9-mobl \
    --to=philip.li@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=mm-commits@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