All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Kefeng Wang <wangkefeng.wang@huawei.com>,
	linux-serial@vger.kernel.org, linux-acpi@vger.kernel.org,
	Ken Xue <Ken.Xue@amd.com>
Subject: Re: [PATCH 1/3] ACPI / APD: Provide build-in properties of the UART
Date: Tue, 23 Aug 2016 09:37:08 +0300	[thread overview]
Message-ID: <20160823063708.GC9065@kuha.fi.intel.com> (raw)
In-Reply-To: <201608222208.evSAciq7%fengguang.wu@intel.com>

Hi,

On Mon, Aug 22, 2016 at 11:00:49PM +0800, kbuild test robot wrote:
> Hi Heikki,
> 
> [auto build test ERROR on pm/linux-next]
> [also build test ERROR on v4.8-rc3 next-20160822]
> [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/Heikki-Krogerus/ACPI-APD-Provide-build-in-properties-of-the-UART/20160822-222543
> base:   https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
> config: x86_64-randconfig-x016-201634 (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=x86_64 
> 
> All errors (new ones prefixed by >>):
> 
>    drivers/acpi/acpi_apd.c: In function 'acpi_apd_setup':
> >> drivers/acpi/acpi_apd.c:71:11: error: 'struct apd_private_data' has no member named 'properties'
>      if (pdata->properties)
>               ^~
>    drivers/acpi/acpi_apd.c:73:16: error: 'struct apd_private_data' has no member named 'properties'
>               pdata->properties);
>                    ^~
> 
> vim +71 drivers/acpi/acpi_apd.c
> 
>     65						dev_name(&pdata->adev->dev),
>     66						NULL, 0, dev_desc->fixed_clk_rate);
>     67			clk_register_clkdev(clk, NULL, dev_name(&pdata->adev->dev));
>     68			pdata->clk = clk;
>     69		}
>     70	
>   > 71		if (pdata->properties)

Thanks, I'll fix it. I did not get compiler error from this? Weird.


Br,

-- 
heikki

  reply	other threads:[~2016-08-23  6:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-22 14:24 [PATCH 0/3] serial: dw8250: ACPI tuning Heikki Krogerus
2016-08-22 14:24 ` [PATCH 1/3] ACPI / APD: Provide build-in properties of the UART Heikki Krogerus
2016-08-22 15:00   ` kbuild test robot
2016-08-23  6:37     ` Heikki Krogerus [this message]
2016-08-22 16:01   ` kbuild test robot
2016-08-22 14:24 ` [PATCH 2/3] ACPI / LPSS: " Heikki Krogerus
2016-08-23  7:03   ` Mika Westerberg
2016-08-22 14:24 ` [PATCH 3/3] serial: 8250_dw: Add quirk for APM X-Gene SoC Heikki Krogerus

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=20160823063708.GC9065@kuha.fi.intel.com \
    --to=heikki.krogerus@linux.intel.com \
    --cc=Ken.Xue@amd.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kbuild-all@01.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=rjw@rjwysocki.net \
    --cc=wangkefeng.wang@huawei.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.