mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: kbuild-all@01.org, Linus Walleij <linus.walleij@linaro.org>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-gpio@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, Bartosz Golaszewski <brgl@bgdev.pl>
Subject: Re: [PATCH] gpiolib: add hogs support for machine code
Date: Wed, 11 Apr 2018 01:05:23 +0800	[thread overview]
Message-ID: <201804110047.jKfmWBhd%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180410124029.2915-1-brgl@bgdev.pl>

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

Hi Bartosz,

I love your patch! Yet something to improve:

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

url:    https://github.com/0day-ci/linux/commits/Bartosz-Golaszewski/gpiolib-add-hogs-support-for-machine-code/20180410-232047
base:   https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git for-next
config: i386-randconfig-a0-201814 (attached as .config)
compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All errors (new ones prefixed by >>):

   In file included from drivers//mfd/sm501.c:23:0:
>> include/linux/gpio/machine.h:56:19: error: field 'dflags' has incomplete type
     enum gpiod_flags dflags;
                      ^

vim +/dflags +56 include/linux/gpio/machine.h

    41	
    42	/**
    43	 * struct gpiod_hog - GPIO line hog table
    44	 * @chip_label: name of the chip the GPIO belongs to
    45	 * @chip_hwnum: hardware number (i.e. relative to the chip) of the GPIO
    46	 * @line_name: consumer name for the hogged line
    47	 * @lflags: mask of GPIO lookup flags
    48	 * @dflags: GPIO flags used to specify the direction and value
    49	 */
    50	struct gpiod_hog {
    51		struct list_head list;
    52		const char *chip_label;
    53		u16 chip_hwnum;
    54		const char *line_name;
    55		enum gpio_lookup_flags lflags;
  > 56		enum gpiod_flags dflags;
    57	};
    58	

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

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

  reply	other threads:[~2018-04-10 17:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-10 12:40 Bartosz Golaszewski
2018-04-10 17:05 ` kbuild test robot [this message]
2018-04-10 20:31   ` Bartosz Golaszewski

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=201804110047.jKfmWBhd%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=brgl@bgdev.pl \
    --cc=corbet@lwn.net \
    --cc=kbuild-all@01.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®