All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Mark Brown <broonie@kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Ryan Roberts <ryan.roberts@arm.com>,
	Will Deacon <will@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Philip Li <philip.li@intel.com>
Subject: Re: linux-next: build failure after merge of the mm-hotfixes tree
Date: Tue, 21 Apr 2026 17:04:55 +0200	[thread overview]
Message-ID: <14d0f4e4-45cc-4172-8a43-a0a14bacfedf@kernel.org> (raw)
In-Reply-To: <20260421074819.89c55503b44afcba46df5d31@linux-foundation.org>

> 
>>> - coverage is mm-new is poor - for example, this error probably
>>>   wouldn't have been found until Mark grabbed the patch via mm-hotfixes.
>>
>> I get daily build reports against mm-new, for example, mail from this night
> 
> Aren't you lucky ;).  Is it possible to add a cc:mm-commits to that script?
> 

Hehe, if it finds something that is broken, it sends mails to the list
like [1]

I only get the build summaries. While we were testing the 0day
integration of mm-new, we tried to keep the noise for other to a minimum.

@Phil, could we also Cc mm-commits@vger.kernel.org and Andrew on the
build summaries for mm-new, like the one from yesterday:

"[akpm-mm:mm-new] BUILD SUCCESS f4279f87cd6c82ebdaccdc56f38e7b80ca7fcc03"

Thanks!

[1] https://lore.kernel.org/all/202604171841.MGvqbmu8-lkp@intel.com/

-- 
Cheers,

David

  reply	other threads:[~2026-04-21 15:04 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-21 12:59 linux-next: build failure after merge of the mm-hotfixes tree Mark Brown
2026-04-21 13:06 ` David Hildenbrand (Arm)
2026-04-21 13:21   ` Mark Brown
2026-04-21 13:28     ` David Hildenbrand (Arm)
2026-04-21 13:34     ` Mark Brown
2026-04-21 13:42       ` David Hildenbrand (Arm)
2026-04-21 14:17         ` Andrew Morton
2026-04-21 14:20           ` David Hildenbrand (Arm)
2026-04-21 14:28             ` Andrew Morton
2026-04-21 14:35               ` David Hildenbrand (Arm)
2026-04-21 14:48                 ` Andrew Morton
2026-04-21 15:04                   ` David Hildenbrand (Arm) [this message]
2026-04-21 16:04                     ` Philip Li
2026-04-21 16:21                       ` David Hildenbrand (Arm)
2026-04-21 14:28           ` Mark Brown
2026-04-21 14:39             ` David Hildenbrand (Arm)
  -- strict thread matches above, loose matches on Subject: below --
2025-12-07 21:35 Stephen Rothwell
2025-12-08 10:30 ` Maciej Wieczor-Retman
2025-12-09  1:37   ` Andrew Morton
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=14d0f4e4-45cc-4172-8a43-a0a14bacfedf@kernel.org \
    --to=david@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=philip.li@intel.com \
    --cc=ryan.roberts@arm.com \
    --cc=will@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.