Linux Input/HID development
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
Cc: somyaanand214@gmail.com, linux-fbdev@vger.kernel.org,
	dmitry.torokhov@gmail.com, peter.senna@gmail.com,
	linux-kernel@vger.kernel.org, yalin.wang2010@gmail.com,
	ricardo.ribalda@gmail.com, devel@driverdev.osuosl.org,
	dbaryshkov@gmail.com, tomi.valkeinen@ti.com,
	linux-input@vger.kernel.org, plagnioj@jcrosoft.com,
	dan.carpenter@oracle.com, linux-pm@vger.kernel.org,
	jslaby@suse.com, alan@linux.intel.com,
	gregkh@linuxfoundation.org, sre@kernel.org, kbuild-all@01.org,
	joe@perches.com, dwmw2@infradead.org
Subject: Re: [PATCH] goldfish: add goldfish match node for dt driver probe
Date: Fri, 6 Nov 2015 13:33:53 +0800	[thread overview]
Message-ID: <201511061352.dIxF87hf%fengguang.wu@intel.com> (raw)
In-Reply-To: <1446787441-18846-1-git-send-email-yalin.wang2010@gmail.com>

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

Hi yalin,

[auto build test ERROR on staging/staging-testing]
[also build test ERROR on v4.3 next-20151105]

url:    https://github.com/0day-ci/linux/commits/yalin-wang/goldfish-add-goldfish-match-node-for-dt-driver-probe/20151106-132647
config: x86_64-allyesconfig (attached as .config)
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All errors (new ones prefixed by >>):

>> drivers/staging/goldfish/goldfish_nand.c:446:3: error: request for member 'of_match_table' in something not a structure or union
      .of_match_table = of_match_ptr(goldfish_nand_match),
      ^

vim +/of_match_table +446 drivers/staging/goldfish/goldfish_nand.c

   440	
   441	static struct platform_driver goldfish_nand_driver = {
   442		.probe		= goldfish_nand_probe,
   443		.remove		= goldfish_nand_remove,
   444		.driver = {
   445			.name = "goldfish_nand"
 > 446			.of_match_table	= of_match_ptr(goldfish_nand_match),
   447		}
   448	};
   449	

---
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: 50533 bytes --]

[-- Attachment #3: Type: text/plain, Size: 169 bytes --]

_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

      reply	other threads:[~2015-11-06  5:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-06  5:24 [PATCH] goldfish: add goldfish match node for dt driver probe yalin wang
2015-11-06  5:33 ` 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=201511061352.dIxF87hf%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=alan@linux.intel.com \
    --cc=dan.carpenter@oracle.com \
    --cc=dbaryshkov@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=joe@perches.com \
    --cc=jslaby@suse.com \
    --cc=kbuild-all@01.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=peter.senna@gmail.com \
    --cc=plagnioj@jcrosoft.com \
    --cc=ricardo.ribalda@gmail.com \
    --cc=somyaanand214@gmail.com \
    --cc=sre@kernel.org \
    --cc=tomi.valkeinen@ti.com \
    --cc=yalin.wang2010@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox