[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180320074022.GA8152@kroah.com>
Date: Tue, 20 Mar 2018 08:40:22 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-kernel@...r.kernel.org, ben.hutchings@...ethink.co.uk,
shuahkh@....samsung.com, lkft-triage@...ts.linaro.org,
patches@...nelci.org, stable@...r.kernel.org,
akpm@...ux-foundation.org, torvalds@...ux-foundation.org,
linux@...ck-us.net
Subject: Re: [PATCH 4.9 000/241] 4.9.89-stable review
On Tue, Mar 20, 2018 at 08:59:51AM +0800, Dan Rue wrote:
> On Mon, Mar 19, 2018 at 07:04:25PM +0100, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.9.89 release.
> > There are 241 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with these being applied, please
> > let me know.
> >
> > Responses should be made by Wed Mar 21 18:07:03 UTC 2018.
> > Anything received after that time might be too late.
> >
> > The whole patch series can be found in one patch at:
> > https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.9.89-rc1.gz
> > or in the git tree and branch at:
> > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.9.y
> > and the diffstat can be found below.
>
> I needed to revert the following in order to successfully build arm32
> and arm64 with default configs:
>
> 9b18a27ddaa0 ("ARM: dts: silk: Correct clock of DU1")
> 181e698aaf8c ("ARM: dts: r8a7794: Correct clock of DU1")
Should now be fixed.
> 2bbf316eee1b ("soc/tegra: Fix link errors with PMC disabled")
Now dropped, should have not been included, was fixing something from
4.12.
> 0a576d2dfcc6 ("dmaengine: bcm2835-dma: Use vchan_terminate_vdesc() instead of desc_free")
Dropped, I thought I had deleted it earlier, my fault.
> 67ee5b1dfe12 ("clk: sunxi-ng: a33: Add offset and minimum value for DDR1 PLL N factor")
Now dropped.
> 9294024e21e3 ("ARM: DRA7: hwmod_data: Prevent wait_target_disable error for usb_otg_ss")
Now dropped.
> I'm not sure the best way to report the specific issues with those, or
> why there have been so many arm32/64-related build issues lately. Let me
> know if you want more details.
This way was just fine. I'll go push out a -rc2 for this tree now, many
thanks.
greg k-h
Powered by blists - more mailing lists