archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <>
To: Constantine Shulyupin <>
	open list <>,, Constantine Shulyupin <>
Subject: Re: [PATCH v3 1/3] fuse: add max_pages option
Date: Wed, 15 Aug 2018 17:21:56 +0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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

Hi Constantine,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on fuse/for-next]
[also build test ERROR on v4.18 next-20180814]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

base: for-next
config: x86_64-rhel (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
        # save the attached .config to linux build tree
        make ARCH=x86_64 

Note: the linux-review/Constantine-Shulyupin/fuse-add-max_pages-option/20180815-132537 HEAD a01ed7faa3c2a69ef01952ff908d28718edb056c builds fine.
      It only hurts bisectibility.

All errors (new ones prefixed by >>):

>> ERROR: "pipe_max_size" [fs/fuse/fuse.ko] undefined!

0-DAY kernel test infrastructure                Open Source Technology Center                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 40815 bytes --]

      parent reply	other threads:[~2018-08-15 12:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-14 21:17 [PATCH v3 1/3] fuse: add max_pages option Constantine Shulyupin
2018-08-14 21:17 ` [PATCH v3 2/3] " Constantine Shulyupin
2018-08-14 21:17 ` [PATCH v3 3/3] fuse: export pipe_max_size for max_pages Constantine Shulyupin
2018-08-15  7:56 ` [PATCH v3 1/3] fuse: add max_pages option Miklos Szeredi
2018-08-15  9:21 ` kbuild test robot [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \

* 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).