From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: kernel-janitors@vger.kernel.org
Subject: Re: [char-misc:char-misc-next 17/29] drivers/w1/masters/w1-gpio.c:72:7: error: 'struct w1_gpio_platf
Date: Thu, 16 Aug 2012 18:16:50 +0000 [thread overview]
Message-ID: <20120816181650.GA31978@kroah.com> (raw)
In-Reply-To: <502d3586.bFwIUoxLKw1xpfKw%fengguang.wu@intel.com>
On Fri, Aug 17, 2012 at 02:01:42AM +0800, Fengguang Wu wrote:
> Hi Daniel,
>
> FYI, kernel build failed on
>
> tree: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git char-misc-next
> head: 877cdf3949cc67d00677a1dfb913001f324ac40d
> commit: 5f3d1382e3ca39a54032784414f0ad4e7078b37e [17/29] onewire: w1-gpio: add DT bindings
> config: i386-randconfig-k729 (attached as .config)
>
> All related error/warning messages:
>
> drivers/w1/masters/w1-gpio.c: In function 'w1_gpio_probe_dt':
> drivers/w1/masters/w1-gpio.c:72:7: error: 'struct w1_gpio_platform_data' has no member named 'ext_pullup_enable_pin'
>
> vim +72 drivers/w1/masters/w1-gpio.c
> 69 pdata->is_open_drain = 1;
> 70
> 71 pdata->pin = of_get_gpio(np, 0);
> > 72 pdata->ext_pullup_enable_pin = of_get_gpio(np, 1);
> 73 pdev->dev.platform_data = pdata;
> 74
> 75 return 0;
>
> ---
> 0-DAY kernel build testing backend Open Source Technology Centre
You aren't kidding about 0 day kernel build testing, very nice job.
Yes, I got patches mixed up again, out of order, my fault, the patch
after this one should fix the build, right?
If not, please let us know.
greg k-h
next prev parent reply other threads:[~2012-08-16 18:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 18:01 [char-misc:char-misc-next 17/29] drivers/w1/masters/w1-gpio.c:72:7: error: 'struct w1_gpio_platform_ Fengguang Wu
2012-08-16 18:16 ` Greg Kroah-Hartman [this message]
2012-08-16 23:35 ` [char-misc:char-misc-next 17/29] drivers/w1/masters/w1-gpio.c:72:7: error: 'struct w1_gpio_platf Fengguang Wu
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=20120816181650.GA31978@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=kernel-janitors@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;
as well as URLs for NNTP newsgroup(s).