From: Andrew Morton <akpm@linux-foundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Liam Howlett <liam.howlett@oracle.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: run time warning after merge of the mm tree
Date: Tue, 26 Jul 2022 11:45:13 -0700 [thread overview]
Message-ID: <20220726114513.88a691eae4ce4305ad9fead8@linux-foundation.org> (raw)
In-Reply-To: <20220726212340.72499268@canb.auug.org.au>
On Tue, 26 Jul 2022 21:23:40 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> I am wondering if maybe the -unstable parts of the mm tree should be
> dropped in the last week before the merge window opens on the
> understanding that those changes may be too late for this release?
Yes, we've been discussing that. I'll temporarily drop mapletree
today, along with some other series which are significantly dependent
upon it.
prev parent reply other threads:[~2022-07-26 18:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 11:23 linux-next: run time warning after merge of the mm tree Stephen Rothwell
2022-07-26 18:32 ` Liam Howlett
2022-07-26 20:51 ` Liam Howlett
2022-07-26 22:25 ` Stephen Rothwell
2022-07-26 18:45 ` Andrew Morton [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=20220726114513.88a691eae4ce4305ad9fead8@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=liam.howlett@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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