linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Zi Yan" <zi.yan@cs.rutgers.edu>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kbuild test robot <lkp@intel.com>,
	kbuild-all@01.org, n-horiguchi@ah.jp.nec.com,
	kirill.shutemov@linux.intel.com, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, minchan@kernel.org, vbabka@suse.cz,
	mgorman@techsingularity.net, mhocko@kernel.org,
	khandual@linux.vnet.ibm.com, dnellans@nvidia.com,
	dave.hansen@intel.com
Subject: Re: [PATCH v6 05/10] mm: thp: enable thp migration in generic path
Date: Thu, 25 May 2017 19:35:40 -0400	[thread overview]
Message-ID: <F8017E2F-74FB-4D9F-9900-D4D1085E1F30@cs.rutgers.edu> (raw)
In-Reply-To: <20170525154328.61a2b2ceef37183895d5ce43@linux-foundation.org>

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

On 25 May 2017, at 18:43, Andrew Morton wrote:

> On Thu, 25 May 2017 13:19:54 -0400 "Zi Yan" <zi.yan@cs.rutgers.edu> wrote:
>
>> On 25 May 2017, at 13:06, kbuild test robot wrote:
>>
>>> Hi Zi,
>>>
>>> [auto build test WARNING on mmotm/master]
>>> [also build test WARNING on v4.12-rc2 next-20170525]
>>> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
>>>
>>> url:    https://github.com/0day-ci/linux/commits/Zi-Yan/mm-page-migration-enhancement-for-thp/20170526-003749
>>> base:   git://git.cmpxchg.org/linux-mmotm.git master
>>> config: i386-randconfig-x016-201721 (attached as .config)
>>> compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
>>> reproduce:
>>>         # save the attached .config to linux build tree
>>>         make ARCH=i386
>>>
>>> All warnings (new ones prefixed by >>):
>>>
>>>    In file included from fs/proc/task_mmu.c:15:0:
>>>    include/linux/swapops.h: In function 'swp_entry_to_pmd':
>>>>> include/linux/swapops.h:222:16: warning: missing braces around initializer [-Wmissing-braces]
>>>      return (pmd_t){{ 0 }};
>>>                    ^
>>
>> The braces are added to eliminate the warning from "m68k-linux-gcc (GCC) 4.9.0",
>> which has the bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53119.
>
> I think we'd prefer to have a warning on m68k than on i386!  Is there
> something smarter we can do here?

I will remove the braces in the next version.

The bug is present in gcc 4.8 and 4.9 and m68k has newer gcc to use,
so kbuild test robot needs to upgrade its m68k gcc (maybe it has done it).

—
Best Regards,
Yan Zi

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 496 bytes --]

  reply	other threads:[~2017-05-25 23:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-25 14:19 [PATCH v6 00/10] mm: page migration enhancement for thp Zi Yan
2017-05-25 14:19 ` [PATCH v6 01/10] mm: mempolicy: add queue_pages_required() Zi Yan
2017-05-25 14:19 ` [PATCH v6 02/10] mm: x86: move _PAGE_SWP_SOFT_DIRTY from bit 7 to bit 1 Zi Yan
2017-05-25 14:19 ` [PATCH v6 03/10] mm: thp: introduce separate TTU flag for thp freezing Zi Yan
2017-05-25 14:19 ` [PATCH v6 04/10] mm: thp: introduce CONFIG_ARCH_ENABLE_THP_MIGRATION Zi Yan
2017-05-25 14:19 ` [PATCH v6 05/10] mm: thp: enable thp migration in generic path Zi Yan
2017-05-25 17:06   ` kbuild test robot
2017-05-25 17:19     ` Zi Yan
2017-05-25 22:43       ` Andrew Morton
2017-05-25 23:35         ` Zi Yan [this message]
2017-05-26  0:58           ` Fengguang Wu
2017-05-29 14:13           ` Zi Yan
2017-05-25 14:19 ` [PATCH v6 06/10] mm: thp: check pmd migration entry in common path Zi Yan
2017-05-25 17:00   ` kbuild test robot
2017-05-25 17:25   ` kbuild test robot
2017-05-25 14:19 ` [PATCH v6 07/10] mm: soft-dirty: keep soft-dirty bits over thp migration Zi Yan
2017-05-25 14:19 ` [PATCH v6 08/10] mm: mempolicy: mbind and migrate_pages support " Zi Yan
2017-05-25 14:19 ` [PATCH v6 09/10] mm: migrate: move_pages() supports " Zi Yan
2017-05-25 14:19 ` [PATCH v6 10/10] mm: memory_hotplug: memory hotremove " Zi Yan

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=F8017E2F-74FB-4D9F-9900-D4D1085E1F30@cs.rutgers.edu \
    --to=zi.yan@cs.rutgers.edu \
    --cc=akpm@linux-foundation.org \
    --cc=dave.hansen@intel.com \
    --cc=dnellans@nvidia.com \
    --cc=kbuild-all@01.org \
    --cc=khandual@linux.vnet.ibm.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=mgorman@techsingularity.net \
    --cc=mhocko@kernel.org \
    --cc=minchan@kernel.org \
    --cc=n-horiguchi@ah.jp.nec.com \
    --cc=vbabka@suse.cz \
    /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).