linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Re: linux-next: Tree for Jan 31 (drivers/i2c/busses/i2c-stm32f7.c)
       [not found] <20200131150606.34caeb7c@canb.auug.org.au>
@ 2020-01-31  7:49 ` Randy Dunlap
  2020-01-31  7:52   ` Wolfram Sang
  0 siblings, 1 reply; 2+ messages in thread
From: Randy Dunlap @ 2020-01-31  7:49 UTC (permalink / raw)
  To: Stephen Rothwell, Linux Next Mailing List
  Cc: Linux Kernel Mailing List, M'boumba Cedric Madianga,
	Wolfram Sang, linux-i2c@vger.kernel.org

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.
> 
> Changes since 20200130:
> 
> The amdgpu tree lost its build failure.
> 
> The akpm-current tree gained a build failure due to an interaction with
> the nfsd tree for which I have revertd a commit.
> 
> Non-merge commits (relative to Linus' tree): 3654
>  3320 files changed, 145104 insertions(+), 53102 deletions(-)
> 
> ----------------------------------------------------------------------------
> 
> I have created today's linux-next tree at
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> (patches at http://www.kernel.org/pub/linux/kernel/next/ ).  If you
> are tracking the linux-next tree using git, you should not use "git pull"
> to do so as that will try to merge the new linux-next release with the
> old one.  You should use "git fetch" and checkout or reset to the new
> master.
> 
> You can see which trees have been included by looking in the Next/Trees
> file in the source.  There are also quilt-import.log and merge.log
> files in the Next directory.  Between each merge, the tree was built
> with a ppc64_defconfig for powerpc, an allmodconfig for x86_64, a
> multi_v7_defconfig for arm and a native build of tools/perf. After
> the final fixups (if any), I do an x86_64 modules_install followed by
> builds for x86_64 allnoconfig, powerpc allnoconfig (32 and 64 bit),
> ppc44x_defconfig, allyesconfig and pseries_le_defconfig and i386, sparc
> and sparc64 defconfig. And finally, a simple boot test of the powerpc
> pseries_le_defconfig kernel in qemu (with and without kvm enabled).
> 
> Below is a summary of the state of the merge.
> 
> I am currently merging 315 trees (counting Linus' and 78 trees of bug
> fix patches pending for the current merge release).
> 
> Stats about the size of the tree over time can be seen at
> http://neuling.org/linux-next-size.html .
> 
> Status of my local build tests will be at
> http://kisskb.ellerman.id.au/linux-next .  If maintainers want to give
> advice about cross compilers/configs that work, we are always open to add
> more builds.
> 
> Thanks to Randy Dunlap for doing many randconfig builds.  And to Paul
> Gortmaker for triage and bug fixes.
> 

on i386:

when CONFIG_I2C is not set/enabled:

../drivers/i2c/busses/i2c-stm32f7.c: In function ‘stm32f7_i2c_suspend’:
../drivers/i2c/busses/i2c-stm32f7.c:2199:44: error: ‘struct dev_pm_info’ has no member named ‘wakeup_path’
  if (!device_may_wakeup(dev) && !dev->power.wakeup_path) {
                                            ^
../drivers/i2c/busses/i2c-stm32f7.c: In function ‘stm32f7_i2c_resume’:
../drivers/i2c/busses/i2c-stm32f7.c:2218:44: error: ‘struct dev_pm_info’ has no member named ‘wakeup_path’
  if (!device_may_wakeup(dev) && !dev->power.wakeup_path) {
                                            ^


-- 
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: linux-next: Tree for Jan 31 (drivers/i2c/busses/i2c-stm32f7.c)
  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
  0 siblings, 0 replies; 2+ messages in thread
From: Wolfram Sang @ 2020-01-31  7:52 UTC (permalink / raw)
  To: Randy Dunlap
  Cc: Stephen Rothwell, Linux Next Mailing List,
	Linux Kernel Mailing List, M'boumba Cedric Madianga,
	linux-i2c@vger.kernel.org

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

> on i386:
> 
> when CONFIG_I2C is not set/enabled:
> 
> ../drivers/i2c/busses/i2c-stm32f7.c: In function ‘stm32f7_i2c_suspend’:
> ../drivers/i2c/busses/i2c-stm32f7.c:2199:44: error: ‘struct dev_pm_info’ has no member named ‘wakeup_path’
>   if (!device_may_wakeup(dev) && !dev->power.wakeup_path) {
>                                             ^
> ../drivers/i2c/busses/i2c-stm32f7.c: In function ‘stm32f7_i2c_resume’:
> ../drivers/i2c/busses/i2c-stm32f7.c:2218:44: error: ‘struct dev_pm_info’ has no member named ‘wakeup_path’
>   if (!device_may_wakeup(dev) && !dev->power.wakeup_path) {

I dropped/reverted this patch already. Sorry for the inconvenience!


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2020-01-31  7:52 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <20200131150606.34caeb7c@canb.auug.org.au>
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

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).