All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Sterba <dsterba@suse.cz>
Cc: Omar Sandoval <osandov@osandov.com>,
	Michal Hocko <mhocko@kernel.org>,
	lkp@01.org, Omar Sandoval <osandov@fb.com>,
	Vinnie Magro <vmagro@fb.com>,
	kernel test robot <xiaolong.ye@intel.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [lkp-robot] [btrfs]  beeeccca9b: WARNING:at_mm/util.c:#kvmalloc_node
Date: Mon, 5 Jun 2017 22:11:38 +1000	[thread overview]
Message-ID: <20170605221138.1c6df396@canb.auug.org.au> (raw)
In-Reply-To: <20170605114306.GR12135@suse.cz>

Hi David,

On Mon, 5 Jun 2017 13:43:06 +0200 David Sterba <dsterba@suse.cz> wrote:
>
> Now fixed, sorry. Top commit 736202ae51c50a6063087011073e91b6a6ae92e9. I
> didn't notice the patch got back to for-next through another branch.

Ah ha.  Thanks.

-- 
Cheers,
Stephen Rothwell

WARNING: multiple messages have this Message-ID (diff)
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: lkp@lists.01.org
Subject: Re: [lkp-robot] [btrfs] beeeccca9b: WARNING:at_mm/util.c:#kvmalloc_node
Date: Mon, 05 Jun 2017 22:11:38 +1000	[thread overview]
Message-ID: <20170605221138.1c6df396@canb.auug.org.au> (raw)
In-Reply-To: <20170605114306.GR12135@suse.cz>

[-- Attachment #1: Type: text/plain, Size: 290 bytes --]

Hi David,

On Mon, 5 Jun 2017 13:43:06 +0200 David Sterba <dsterba@suse.cz> wrote:
>
> Now fixed, sorry. Top commit 736202ae51c50a6063087011073e91b6a6ae92e9. I
> didn't notice the patch got back to for-next through another branch.

Ah ha.  Thanks.

-- 
Cheers,
Stephen Rothwell

  reply	other threads:[~2017-06-05 12:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-31  6:30 [lkp-robot] [btrfs] beeeccca9b: WARNING:at_mm/util.c:#kvmalloc_node kernel test robot
2017-05-31  6:30 ` kernel test robot
2017-05-31  6:51 ` Michal Hocko
2017-05-31  6:51   ` Michal Hocko
2017-05-31  9:12   ` Omar Sandoval
2017-05-31  9:12     ` Omar Sandoval
2017-05-31  9:19     ` Michal Hocko
2017-05-31  9:19       ` Michal Hocko
2017-05-31  9:29       ` Omar Sandoval
2017-05-31  9:29         ` Omar Sandoval
2017-05-31 10:30         ` Michal Hocko
2017-05-31 10:30           ` Michal Hocko
2017-05-31 14:58         ` David Sterba
2017-05-31 14:58           ` David Sterba
2017-06-05  3:30           ` Stephen Rothwell
2017-06-05  3:30             ` Stephen Rothwell
2017-06-05 11:43             ` David Sterba
2017-06-05 11:43               ` David Sterba
2017-06-05 12:11               ` Stephen Rothwell [this message]
2017-06-05 12:11                 ` 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=20170605221138.1c6df396@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=dsterba@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=mhocko@kernel.org \
    --cc=osandov@fb.com \
    --cc=osandov@osandov.com \
    --cc=vmagro@fb.com \
    --cc=xiaolong.ye@intel.com \
    /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.