stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Chris Paterson <Chris.Paterson2@renesas.com>
Cc: Sasha Levin <sashal@kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>
Subject: Re: Linux 4.19.89-rc1 5944fcdd errors
Date: Wed, 11 Dec 2019 14:45:45 +0100	[thread overview]
Message-ID: <20191211134545.GC523125@kroah.com> (raw)
In-Reply-To: <TYAPR01MB22852454802BAB486871D944B75A0@TYAPR01MB2285.jpnprd01.prod.outlook.com>

On Wed, Dec 11, 2019 at 10:52:44AM +0000, Chris Paterson wrote:
> Hello Greg,
> 
> [...]
> 
> > > > That's a lot, are these all new?
> > >
> > > I've only just started building with this config in our CI setup, but
> > > building the dtbs locally with v4.19.88 didn't produce these results
> > > for me (and building locally with v4.19.89-rc1 does result in the
> > > above issues).
> > 
> > Any chance you can run 'git bisect' to track down the offending patch?
> 
> The two dtbs that fail to build are fixed by reverting by the patches below:
> 
> > allwinner/sun50i-a64-pinebook.dtb
> ea03518a3123 ("arm64: dts: allwinner: a64: enable sound on Pinebook")

Now dropped.

> > qcom/sdm845-mtp.dtb
> d0a925e2060d ("arm64: dts: qcom: sdm845-mtp: Mark protected gcc clocks")

Now dropped.

> The rest of the dtbs just had warnings, all produced by the patch below:
> 
> > arm/juno.dtb
> > qcom/apq8016-sbc.dtb
> > arm/juno-r2.dtb
> > arm/juno-r1.dtb
> > hisilicon/hi6220-hikey.dtb
> > qcom/msm8916-mtp.dtb
> > qcom/msm8916-mtp.dtb
> 3fa6a276a4bd ("kbuild: Enable dtc graph_port warning by default")

Now dropped as well.

I'll push out new kernels in a bit, thanks for this info.

greg k-h

      parent reply	other threads:[~2019-12-11 13:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-09 16:29 Linux 4.19.89-rc1 5944fcdd errors Chris Paterson
2019-12-09 16:34 ` Chris Paterson
2019-12-09 16:53 ` Naresh Kamboju
2019-12-09 17:02 ` Greg Kroah-Hartman
2019-12-09 17:04 ` Greg Kroah-Hartman
2019-12-09 17:36 ` Greg Kroah-Hartman
2019-12-09 21:56   ` Chris Paterson
2019-12-10  7:35     ` Greg Kroah-Hartman
2019-12-10 14:42       ` Chris Paterson
2019-12-10 14:55         ` Greg Kroah-Hartman
2019-12-10 15:20           ` Chris Paterson
2019-12-10 20:59             ` Greg Kroah-Hartman
2019-12-11 10:52               ` Chris Paterson
2019-12-11 12:19                 ` Chen-Yu Tsai
2019-12-11 13:45                 ` Greg Kroah-Hartman [this message]

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=20191211134545.GC523125@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Chris.Paterson2@renesas.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=sashal@kernel.org \
    --cc=stable@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).