From: Chen-Yu Tsai <wens@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
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 20:19:36 +0800 [thread overview]
Message-ID: <CAGb2v66mXBtyypam9iPbT_=cpm-ZYSpFqDBA9f3mxM9ME8q-ug@mail.gmail.com> (raw)
In-Reply-To: <TYAPR01MB22852454802BAB486871D944B75A0@TYAPR01MB2285.jpnprd01.prod.outlook.com>
On Wed, Dec 11, 2019 at 6:52 PM Chris Paterson
<Chris.Paterson2@renesas.com> 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")
I suggest dropping this if possible. It depends on another dtsi patch,
ec4a95409d5c arm64: dts: allwinner: a64: add nodes necessary for
analog sound support
and multiple driver patches
55b407f6468c ASoC: sun8i-codec-analog: split regmap code into
separate driver
42371f327df0 ASoC: sunxi: Add new driver for Allwinner A64 codec's
analog path controls
7e95aac96b55 ASoC: sunxi: allow the sun8i-codec driver to be built on ARM64
66ecce332538 ASoC: sun4i-i2s: Add compatibility with A64 codec I2S
... (there quite a few more)
to actually work. Quite sure those aren't backportable since one is over
four hundred lines.
Regards
ChenYu
WARNING: multiple messages have this Message-ID (diff)
From: wens@kernel.org (Chen-Yu Tsai)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Linux 4.19.89-rc1 5944fcdd errors
Date: Wed, 11 Dec 2019 20:19:36 +0800 [thread overview]
Message-ID: <CAGb2v66mXBtyypam9iPbT_=cpm-ZYSpFqDBA9f3mxM9ME8q-ug@mail.gmail.com> (raw)
In-Reply-To: <TYAPR01MB22852454802BAB486871D944B75A0@TYAPR01MB2285.jpnprd01.prod.outlook.com>
On Wed, Dec 11, 2019 at 6:52 PM Chris Paterson
<Chris.Paterson2@renesas.com> 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")
I suggest dropping this if possible. It depends on another dtsi patch,
ec4a95409d5c arm64: dts: allwinner: a64: add nodes necessary for
analog sound support
and multiple driver patches
55b407f6468c ASoC: sun8i-codec-analog: split regmap code into
separate driver
42371f327df0 ASoC: sunxi: Add new driver for Allwinner A64 codec's
analog path controls
7e95aac96b55 ASoC: sunxi: allow the sun8i-codec driver to be built on ARM64
66ecce332538 ASoC: sun4i-i2s: Add compatibility with A64 codec I2S
... (there quite a few more)
to actually work. Quite sure those aren't backportable since one is over
four hundred lines.
Regards
ChenYu
next prev parent reply other threads:[~2019-12-11 12:19 UTC|newest]
Thread overview: 26+ 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:34 ` [cip-dev] " Chris Paterson
2019-12-09 16:53 ` Naresh Kamboju
2019-12-09 16:53 ` [cip-dev] " 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-09 21:56 ` [cip-dev] " Chris Paterson
2019-12-10 7:35 ` Greg Kroah-Hartman
2019-12-10 7:35 ` [cip-dev] " Greg Kroah-Hartman
2019-12-10 14:42 ` Chris Paterson
2019-12-10 14:42 ` [cip-dev] " Chris Paterson
2019-12-10 14:55 ` Greg Kroah-Hartman
2019-12-10 14:55 ` [cip-dev] " Greg Kroah-Hartman
2019-12-10 15:20 ` Chris Paterson
2019-12-10 15:20 ` [cip-dev] " Chris Paterson
2019-12-10 20:59 ` Greg Kroah-Hartman
2019-12-10 20:59 ` [cip-dev] " Greg Kroah-Hartman
2019-12-11 10:52 ` Chris Paterson
2019-12-11 10:52 ` [cip-dev] " Chris Paterson
2019-12-11 12:19 ` Chen-Yu Tsai [this message]
2019-12-11 12:19 ` Chen-Yu Tsai
2019-12-11 13:45 ` Greg Kroah-Hartman
2019-12-11 13:45 ` [cip-dev] " Greg Kroah-Hartman
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='CAGb2v66mXBtyypam9iPbT_=cpm-ZYSpFqDBA9f3mxM9ME8q-ug@mail.gmail.com' \
--to=wens@kernel.org \
--cc=Chris.Paterson2@renesas.com \
--cc=cip-dev@lists.cip-project.org \
--cc=gregkh@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.