From: Joonsoo Kim <js1304@gmail.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, Andrew Morton <akpm@linux-foundation.org>,
Hugh Dickins <hughd@google.com>,
Johannes Berg <johannes@sipsolutions.net>,
"David S. Miller" <davem@davemloft.net>,
Sunil Goutham <sgoutham@cavium.com>,
Linux Memory Management List <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>
Subject: Re: [PATCH 2/2] mm: rename _count, field of the struct page, to _refcount
Date: Mon, 28 Mar 2016 15:19:49 +0900 [thread overview]
Message-ID: <CAAmzW4OW7c94fN8A=bja8z4xGiWaCupGDixeDGjnau9sDknbZA@mail.gmail.com> (raw)
In-Reply-To: <201603281456.e4kLKip8%fengguang.wu@intel.com>
2016-03-28 15:07 GMT+09:00 kbuild test robot <lkp@intel.com>:
> Hi Joonsoo,
>
> [auto build test ERROR on net/master]
> [also build test ERROR on v4.6-rc1 next-20160327]
> [if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
Hello, bot.
Is there any way to stop further warning if I recognize that there is a mistake?
Thanks.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-03-28 6:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-28 5:59 [PATCH 1/2] mm/page_ref: use page_ref helper instead of direct modification of _count js1304
2016-03-28 5:59 ` [PATCH 2/2] mm: rename _count, field of the struct page, to _refcount js1304
2016-03-28 6:05 ` Joonsoo Kim
2016-03-28 6:07 ` kbuild test robot
2016-03-28 6:19 ` Joonsoo Kim [this message]
2016-03-28 6:11 ` kbuild test robot
2016-03-28 6:14 ` kbuild test robot
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='CAAmzW4OW7c94fN8A=bja8z4xGiWaCupGDixeDGjnau9sDknbZA@mail.gmail.com' \
--to=js1304@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=hughd@google.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=johannes@sipsolutions.net \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=sgoutham@cavium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox