From: Mel Gorman <mgorman@suse.de>
To: Uladzislau Rezki <urezki@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
akpm@linux-foundation.org, hdanton@sina.com, mhocko@suse.com,
mm-commits@vger.kernel.org, npiggin@gmail.com,
oleksiy.avramchenko@sonymobile.com, rostedt@goodmis.org,
willy@infradead.org
Subject: Re: [failures] mm-vmalloc-print-a-warning-message-first-on-failure.patch removed from -mm tree
Date: Thu, 13 May 2021 12:11:53 +0100 [thread overview]
Message-ID: <20210513111153.GL3672@suse.de> (raw)
In-Reply-To: <20210513103156.GA1856@pc638.lan>
On Thu, May 13, 2021 at 12:31:56PM +0200, Uladzislau Rezki wrote:
> On Thu, May 13, 2021 at 08:56:02AM +1000, Stephen Rothwell wrote:
> > Hi Andrew,
> >
> > On Wed, 12 May 2021 13:29:52 -0700 akpm@linux-foundation.org wrote:
> > >
> > > The patch titled
> > > Subject: mm/vmalloc: print a warning message first on failure
> > > has been removed from the -mm tree. Its filename was
> > > mm-vmalloc-print-a-warning-message-first-on-failure.patch
> > >
> > > This patch was dropped because it had testing failures
> >
> > Removed from linux-next.
> >
> What can of testing failures does it trigger? Where can i find the
> details, logs or tracers of it?
https://lore.kernel.org/linux-next/20210512175359.17793d34@canb.auug.org.au/
--
Mel Gorman
SUSE Labs
next prev parent reply other threads:[~2021-05-13 11:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 20:29 [failures] mm-vmalloc-print-a-warning-message-first-on-failure.patch removed from -mm tree akpm
2021-05-12 22:56 ` Stephen Rothwell
2021-05-13 10:31 ` Uladzislau Rezki
2021-05-13 11:11 ` Mel Gorman [this message]
2021-05-13 12:46 ` Uladzislau Rezki
2021-05-13 13:24 ` Uladzislau Rezki
2021-05-13 14:18 ` Mel Gorman
[not found] ` <CA+KHdyXwdkosDYk4bKtRLVodrwUJnq3NN39xuRQzKJSPTn7+bQ@mail.gmail.com>
2021-05-13 15:51 ` Mel Gorman
2021-05-13 20:18 ` Uladzislau Rezki
2021-05-14 10:19 ` Mel Gorman
2021-05-14 11:45 ` Uladzislau Rezki
2021-05-14 13:45 ` Mel Gorman
2021-05-14 14:50 ` Uladzislau Rezki
2021-05-14 15:41 ` Mel Gorman
2021-05-14 17:16 ` Uladzislau Rezki
2021-05-16 17:17 ` Mel Gorman
2021-05-16 20:31 ` Uladzislau Rezki
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=20210513111153.GL3672@suse.de \
--to=mgorman@suse.de \
--cc=akpm@linux-foundation.org \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=mm-commits@vger.kernel.org \
--cc=npiggin@gmail.com \
--cc=oleksiy.avramchenko@sonymobile.com \
--cc=rostedt@goodmis.org \
--cc=sfr@canb.auug.org.au \
--cc=urezki@gmail.com \
--cc=willy@infradead.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.