linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: nvme boot problems after merge of mm-stable tree into linux-next
Date: Tue, 14 Feb 2023 14:29:29 +0700	[thread overview]
Message-ID: <02f796c7-c1d5-2f2b-3385-e72298f5f470@gmail.com> (raw)
In-Reply-To: <07c870d3-5d98-ca51-5de8-034abc631673@roeck-us.net>

On 2/14/23 13:49, Guenter Roeck wrote:
> In next-20230210, the crash happened after the merge of mm-stable.
> In next-20230213, the crash happens after the merge of mm-everything.
> That means both the merge of mm-stable and mm-nonmm-stable are now fine.
> So I would suspect that something in the merge of mm-everything
> interacts with the rest of -next.
> 

OK, thanks!

-- 
An old man doll... just what I always wanted! - Clara



  reply	other threads:[~2023-02-14  7:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ed33b9ff-e6f2-dae8-ede6-59dc3c649ece@roeck-us.net>
2023-02-13 17:47 ` nvme boot problems after merge of mm-stable tree into linux-next Andrew Morton
2023-02-14  2:23   ` Bagas Sanjaya
2023-02-14  4:01     ` Guenter Roeck
2023-02-14  6:20       ` Stephen Rothwell
2023-02-14  6:49         ` Guenter Roeck
2023-02-14  7:29           ` Bagas Sanjaya [this message]
2023-02-26 22:14             ` Stephen Rothwell
2023-02-26 22:53               ` Guenter Roeck
2023-02-26 23:04                 ` 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=02f796c7-c1d5-2f2b-3385-e72298f5f470@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --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;
as well as URLs for NNTP newsgroup(s).