From: Al Viro <viro@ZenIV.linux.org.uk>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: Jan Kara <jack@suse.cz>,
kbuild-all@01.org, linux-fsdevel@vger.kernel.org
Subject: Re: [vfs:work.statx 2/3] fs/udf/symlink.c:189:13: error: initialization from incompatible pointer type
Date: Fri, 3 Mar 2017 09:43:39 +0000 [thread overview]
Message-ID: <20170303094338.GE29622@ZenIV.linux.org.uk> (raw)
In-Reply-To: <201703031752.KorVq8Ir%fengguang.wu@intel.com>
On Fri, Mar 03, 2017 at 05:19:57PM +0800, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.statx
> head: 2335fc954ccf342e854379df1f6e81c3a98cf489
> commit: 8594c345e77db3d0d9aafeb18e475212ce89e58d [2/3] Merge commit 'ad4d05329d' into work.statx
> config: i386-randconfig-x072-201709 (attached as .config)
> compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
> reproduce:
> git checkout 8594c345e77db3d0d9aafeb18e475212ce89e58d
> # save the attached .config to linux build tree
> make ARCH=i386
>
> Note: the vfs/work.statx HEAD 2335fc954ccf342e854379df1f6e81c3a98cf489 builds fine.
> It only hurts bisectibility.
Yes, which is precisely why the pull request had been for rebased-statx and
not work.statx. Alternative would be work.statx-minimal with even more
fixups in merge commit. Identical resulting trees, so the testing in -next
applies to either variant, and rebased-statx has neither backmerges nor
fixups in merge...
prev parent reply other threads:[~2017-03-03 9:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 9:19 [vfs:work.statx 2/3] fs/udf/symlink.c:189:13: error: initialization from incompatible pointer type kbuild test robot
2017-03-03 9:43 ` Al Viro [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=20170303094338.GE29622@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=fengguang.wu@intel.com \
--cc=jack@suse.cz \
--cc=kbuild-all@01.org \
--cc=linux-fsdevel@vger.kernel.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 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.