All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Heiko Schocher <hs@denx.de>
Cc: kbuild-all@01.org, linux-mtd@lists.infradead.org,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	Heiko Schocher <hs@denx.de>,
	Artem Bityutskiy <dedekind1@gmail.com>,
	Richard Weinberger <richard@nod.at>,
	Adrian Hunter <adrian.hunter@intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ubifs: compress lines for immediate return
Date: Sun, 11 Sep 2016 07:29:05 +0800	[thread overview]
Message-ID: <201609110731.RTbz48S3%fengguang.wu@intel.com> (raw)
In-Reply-To: <1473058466-10831-1-git-send-email-hs@denx.de>

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

Hi Masahiro,

[auto build test ERROR on linus/master]
[also build test ERROR on v4.8-rc5 next-20160909]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
[Suggest to use git(>=2.9.0) format-patch --base=<commit> (or --base=auto for convenience) to record what (public, well-known) commit your patch series was built on]
[Check https://git-scm.com/docs/git-format-patch for more information]

url:    https://github.com/0day-ci/linux/commits/Heiko-Schocher/ubifs-compress-lines-for-immediate-return/20160905-145802
config: i386-randconfig-x0-09110426 (attached as .config)
compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All errors (new ones prefixed by >>):

   fs/ubifs/budget.c: In function 'run_gc':
>> fs/ubifs/budget.c:91:9: error: expected expression before '=' token
     return = ubifs_return_leb(c, lnum);
            ^
   fs/ubifs/budget.c:92:1: warning: control reaches end of non-void function [-Wreturn-type]
    }
    ^

vim +91 fs/ubifs/budget.c

    85		up_read(&c->commit_sem);
    86		if (lnum < 0)
    87			return lnum;
    88	
    89		/* GC freed one LEB, return it to lprops */
    90		dbg_budg("GC freed LEB %d", lnum);
  > 91		return = ubifs_return_leb(c, lnum);
    92	}
    93	
    94	/**

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 21949 bytes --]

      parent reply	other threads:[~2016-09-10 23:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-05  6:54 [PATCH v2] ubifs: compress lines for immediate return Heiko Schocher
2016-09-05 12:44 ` Masahiro Yamada
2016-09-05 13:05   ` Heiko Schocher
2016-09-05 13:32     ` Richard Weinberger
2016-09-06  4:37       ` Heiko Schocher
2016-09-05 13:18 ` David Oberhollenzer
2016-09-05 13:26   ` Masahiro Yamada
2016-09-10 23:29 ` 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:
  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=201609110731.RTbz48S3%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=adrian.hunter@intel.com \
    --cc=dedekind1@gmail.com \
    --cc=hs@denx.de \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard@nod.at \
    --cc=yamada.masahiro@socionext.com \
    /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.