public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linaro-kernel@lists.linaro.org
Cc: "Mark Brown" <broonie@kernel.org>,
	"Jisheng Zhang" <jszhang@marvell.com>,
	"Thierry Reding" <thierry.reding@gmail.com>,
	"Antoine Ténart" <antoine.tenart@free-electrons.com>,
	linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	kernel-build-reports@lists.linaro.org
Subject: Re: next-20160906 build: 2 failures 0 warnings (next-20160906)
Date: Tue, 06 Sep 2016 12:53:56 +0200	[thread overview]
Message-ID: <4307762.H85fQucTpI@wuerfel> (raw)
In-Reply-To: <20160906104652.GJ3950@sirena.org.uk>

On Tuesday, September 6, 2016 11:46:52 AM CEST Mark Brown wrote:
> On Tue, Sep 06, 2016 at 09:45:43AM +0100, Build bot for Mark Brown wrote:
> 
> Today's -next fails to build arm and arm64 defconfigs due to:
> 
> > 	arm64-allmodconfig
> > ../drivers/pwm/pwm-berlin.c:245:35: error: 'struct berlin_pwm_chip' has no member named 'chips'
> 
> > 	arm-allmodconfig
> > ../drivers/pwm/pwm-berlin.c:245:35: error: 'struct berlin_pwm_chip' has no member named 'chips'
> 
> due to fd47f104003c6 (pwm: berlin: Add suspend/resume support) which was
> applied yesterday.
> 

I've prepared a patch, will send as soon as I have a clean build again.

	Arnd

  reply	other threads:[~2016-09-06 10:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1bhC0l-0003y3-Ls@optimist>
2016-09-06 10:46 ` next-20160906 build: 2 failures 0 warnings (next-20160906) Mark Brown
2016-09-06 10:53   ` Arnd Bergmann [this message]
2016-09-06 10:53     ` Jisheng Zhang

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=4307762.H85fQucTpI@wuerfel \
    --to=arnd@arndb.de \
    --cc=antoine.tenart@free-electrons.com \
    --cc=broonie@kernel.org \
    --cc=jszhang@marvell.com \
    --cc=kernel-build-reports@lists.linaro.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=thierry.reding@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