From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
S Twiss <stwiss.opensource@diasemi.com>,
"wim@linux-watchdog.org" <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>,
"linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>
Subject: Re: linux-next: Tree for Jan 31 (drivers/watchdog/da9062_wdt.c)
Date: Thu, 30 Jan 2020 23:27:39 -0800 [thread overview]
Message-ID: <ac797eb0-9b0a-d2d3-3a40-3fbd0a8b5ee0@infradead.org> (raw)
In-Reply-To: <20200131150606.34caeb7c@canb.auug.org.au>
On 1/30/20 8:06 PM, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any v5.7 material to your linux-next included
> branches until after v5.6-rc1 has been released.
>
> I am experimenting with a "make htmldocs" build at
> the end of the day, but it currently has an error:
>
> docutils.utils.SystemMessage: Documentation/driver-api/thermal/cpu-idle-cooling.rst:95: (SEVERE/4) Unexpected section title.
I sent a patch for that on 2020-JAN-20 but no one has replied to the patch:
https://lore.kernel.org/linux-pm/712c1152-56b5-307f-b3f3-ed03a30b804a@infradead.org/
> Changes since 20200130:
>
on i386:
when CONFIG_I2C is not set/enabled:
../drivers/watchdog/da9062_wdt.c: In function ‘da9062_wdt_restart’:
../drivers/watchdog/da9062_wdt.c:155:8: error: implicit declaration of function ‘i2c_smbus_write_byte_data’; did you mean ‘i2c_set_clientdata’? [-Werror=implicit-function-declaration]
ret = i2c_smbus_write_byte_data(client, DA9062AA_CONTROL_F,
^~~~~~~~~~~~~~~~~~~~~~~~~
i2c_set_clientdata
cc1: some warnings being treated as errors
make[3]: *** [../scripts/Makefile.build:265: drivers/watchdog/da9062_wdt.o] Error 1
--
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>
next prev parent reply other threads:[~2020-01-31 7:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 4:06 linux-next: Tree for Jan 31 Stephen Rothwell
2020-01-31 7:27 ` Randy Dunlap [this message]
2020-01-31 7:49 ` linux-next: Tree for Jan 31 (drivers/i2c/busses/i2c-stm32f7.c) Randy Dunlap
2020-01-31 7:52 ` Wolfram Sang
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=ac797eb0-9b0a-d2d3-3a40-3fbd0a8b5ee0@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=sfr@canb.auug.org.au \
--cc=stwiss.opensource@diasemi.com \
--cc=wim@linux-watchdog.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).