From: Philip Li <philip.li@intel.com>
To: Jerome Glisse <jglisse@redhat.com>
Cc: Fengguang Wu <fengguang.wu@intel.com>,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
kbuild-all@01.org, Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: [kbuild-all] [mmotm:master 119/211] mm/migrate.c:2184:5: note: in expansion of macro 'MIGRATE_PFN_DEVICE'
Date: Sat, 18 Mar 2017 20:48:55 +0800 [thread overview]
Message-ID: <20170318124855.GA16796@intel.com> (raw)
In-Reply-To: <503478426.8747709.1489790882925.JavaMail.zimbra@redhat.com>
On Fri, Mar 17, 2017 at 06:48:02PM -0400, Jerome Glisse wrote:
> > Hi Andrew,
> >
> > On Thu, Mar 16, 2017 at 08:41:35PM -0700, Andrew Morton wrote:
> > >On Fri, 17 Mar 2017 09:46:30 +0800 kbuild test robot
> > ><fengguang.wu@intel.com> wrote:
> > >
> > >> tree: git://git.cmpxchg.org/linux-mmotm.git master
> > >> head: 8276ddb3c638602509386f1a05f75326dbf5ce09
> > >> commit: a6d9a210db7db40e98f7502608c6f1413c44b9b9 [119/211] mm/hmm/migrate:
> > >> support un-addressable ZONE_DEVICE page in migration
> > >
> > >heh, I think the HMM patchset just scored the world record number of
> > >build errors. Thanks for doing this.
> > >
> > >But why didn't we find out earlier than v18? Don't you scoop patchsets
> > >off the mailing list *before* someone merges them into an upstream
> > >tree?
> >
> > Yes we test LKML patches, however not all patches can be successfully
> > applied, so cannot be tested at all.
>
> When patchset fails to apply can the poster get an email so he knows that
> his patchset isn't gonna be build tested.
Hi Jerome, thanks for feedback, sure, we will add this to next quarter's plan
to let author know if his patchset is not tested, also will allow opt in if
some developer wants to have build success notification as well.
>
> Regards,
> Jerome Glisse
> _______________________________________________
> kbuild-all mailing list
> kbuild-all@lists.01.org
> https://lists.01.org/mailman/listinfo/kbuild-all
--
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>
prev parent reply other threads:[~2017-03-18 12:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-17 1:46 [mmotm:master 119/211] mm/migrate.c:2184:5: note: in expansion of macro 'MIGRATE_PFN_DEVICE' kbuild test robot
2017-03-17 3:41 ` Andrew Morton
2017-03-17 4:06 ` [kbuild-all] " Fengguang Wu
2017-03-17 22:48 ` Jerome Glisse
2017-03-18 12:48 ` Philip Li [this message]
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=20170318124855.GA16796@intel.com \
--to=philip.li@intel.com \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=hannes@cmpxchg.org \
--cc=jglisse@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).