From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marek Vasut Date: Wed, 14 Nov 2018 12:54:11 +0100 Subject: [U-Boot] [ANN] U-Boot v2018.11 delayed a day In-Reply-To: <20181114123235.215d876e@crub> References: <20181112214016.GS11247@bill-the-cat> <8668e5b6-00a7-0ebb-8910-b9dd8dabf81b@gmail.com> <20181114123235.215d876e@crub> Message-ID: <40ca45cd-6c90-387a-30bb-22a259f88828@gmail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 11/14/2018 12:32 PM, Anatolij Gustschin wrote: > On Mon, 12 Nov 2018 23:13:29 +0100 > Marek Vasut marek.vasut at gmail.com wrote: > >> On 11/12/2018 10:40 PM, Tom Rini wrote: >>> Hey all, >>> >>> Since Jagan promise a v2 SPI PR for some build fixes that we should have >>> in the release and I believe didn't get them out before the end of his >>> day, I'm letting everyone know now to expect the release tomorrow >>> instead, thanks! >> >> Will anyone have any chance to test those fixes to verify they didn't >> break anything ? >> >> I believe this is yet another manifestation of the problems of the 2 >> month release cycle, which I think is too short and stressful. > > Yes, and patches with fixes sometimes wait long time without review > or testing and miss the release, then people start to complain when > the released code is buggy. What about this [1] patch? Could someone > please review/test it? Can it be applied to v2018.11 ? > > [1] https://patchwork.ozlabs.org/patch/985919 Yes, that's obviously a correct fix. -- Best regards, Marek Vasut