From: Ross Zwisler <ross.zwisler@linux.intel.com>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Souptick Joarder <jrdr.linux@gmail.com>,
kbuild test robot <lkp@intel.com>,
Ross Zwisler <ross.zwisler@linux.intel.com>,
kbuild-all@01.org, mawilcox@microsoft.com,
Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH] fs: dax: Adding new return type vm_fault_t
Date: Wed, 18 Apr 2018 09:41:33 -0600 [thread overview]
Message-ID: <20180418154133.GA30666@linux.intel.com> (raw)
In-Reply-To: <20180418121312.bxblf464hnu7lzbh@wfg-t540p.sh.intel.com>
On Wed, Apr 18, 2018 at 08:13:12PM +0800, Fengguang Wu wrote:
> On Wed, Apr 18, 2018 at 05:08:33PM +0530, Souptick Joarder wrote:
> > Hi Ross,
> >
> > On Wed, Apr 18, 2018 at 2:48 PM, kbuild test robot <lkp@intel.com> wrote:
> > > Hi Souptick,
> > >
> > > Thank you for the patch! Yet something to improve:
> > >
> > > [auto build test ERROR on v4.16]
> > > [cannot apply to linus/master v4.17-rc1 next-20180418]
> >
> > Does it mean patch was initially applied in v4.16 ?
>
> Yes.
>
> > As v4.16 build breaks it fails to apply in v4.17-rc1 and next-20180418 ?
>
> When there is a build fail the robot will apply-and-test the patch on
> more base trees. Here the patch cannot apply to linus/master,
> v4.17-rc1 and next-20180418, so cannot be further tested there.
Right - this needs to be rebased onto the current linux/master, as it
currently collides with a patch from Dan which went into v4.17-rc1.
prev parent reply other threads:[~2018-04-18 15:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 15:35 [PATCH] fs: dax: Adding new return type vm_fault_t Souptick Joarder
2018-04-17 20:26 ` Ross Zwisler
2018-04-17 21:00 ` Matthew Wilcox
2018-04-20 19:21 ` Souptick Joarder
2018-04-20 20:47 ` Matthew Wilcox
2018-04-21 17:26 ` Souptick Joarder
2018-04-18 9:02 ` kbuild test robot
2018-04-18 9:18 ` kbuild test robot
2018-04-18 11:38 ` Souptick Joarder
2018-04-18 12:13 ` Fengguang Wu
2018-04-18 15:41 ` Ross Zwisler [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=20180418154133.GA30666@linux.intel.com \
--to=ross.zwisler@linux.intel.com \
--cc=fengguang.wu@intel.com \
--cc=jrdr.linux@gmail.com \
--cc=kbuild-all@01.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mawilcox@microsoft.com \
--cc=viro@zeniv.linux.org.uk \
/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.