From: Yinghai Lu <yinghai@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kbuild test robot <fengguang.wu@intel.com>,
Linux Memory Management List <linux-mm@kvack.org>,
Johannes Weiner <hannes@cmpxchg.org>,
kbuild-all@01.org
Subject: Re: [mmotm:master 188/230] fs/jffs2/debug.h:69:3: note: in expansion of macro 'pr_debug'
Date: Fri, 20 Jun 2014 14:19:04 -0700 [thread overview]
Message-ID: <CAE9FiQVrOgEcP7wQhLtZZQ3yJ+gbYSE23_UYxJ2GKEWHU=GmWg@mail.gmail.com> (raw)
In-Reply-To: <20140620132904.ec7eced87ff449625ad10d78@linux-foundation.org>
On Fri, Jun 20, 2014 at 1:29 PM, Andrew Morton
<akpm@linux-foundation.org> wrote:
> On Fri, 20 Jun 2014 15:38:30 +0800 kbuild test robot <fengguang.wu@intel.com> wrote:
>
>> tree: git://git.cmpxchg.org/linux-mmotm.git master
>> head: df25ba7db0775d87018e2cd92f26b9b087093840
>> commit: 0b3f61ac78013e35939696ddd63b9b871d11bf72 [188/230] initramfs: support initramfs that is more than 2G
>> config: make ARCH=x86_64 allmodconfig
>>
>> All warnings:
>
> Too many :( I dropped the patch.
Will put my git tree in kernel.org, let's check if test robot can find
more warning.
Hi Fenguang,
Is rest robot going to sweep all new added branches in kernel.org git?
Thanks
Yinghai
--
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:[~2014-06-20 21:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 7:38 kbuild test robot
2014-06-20 20:29 ` Andrew Morton
2014-06-20 21:19 ` Yinghai Lu [this message]
2014-06-21 18:40 ` Fengguang Wu
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='CAE9FiQVrOgEcP7wQhLtZZQ3yJ+gbYSE23_UYxJ2GKEWHU=GmWg@mail.gmail.com' \
--to=yinghai@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox