From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Tue, 9 Apr 2019 07:58:13 -0400 Subject: [U-Boot] [ANN] U-Boot v2019.04-rc4 released In-Reply-To: <20190408130959.GF4664@bill-the-cat> References: <20190319011550.GS8732@bill-the-cat> <16184b24-9e7d-3df0-dc90-2016fb6b08fb@denx.de> <20190408130959.GF4664@bill-the-cat> Message-ID: <20190409115813.GI4664@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Mon, Apr 08, 2019 at 09:09:59AM -0400, Tom Rini wrote: > On Mon, Apr 08, 2019 at 03:07:36PM +0200, Stefan Roese wrote: > > Hi Tom, > > > > On 19.03.19 02:15, Tom Rini wrote: > > >Hey all, > > > > > >So it's release day and I've put up v2019.04-rc4, I've updated git and > > >the tarballs are also up now. > > > > > >Thanks again to having signed tags, between -rc3 and -rc4 we have a good > > >changelog under 'git log --merges v2019.04-rc3..v2019.04-rc4' > > > > > >Right now I have outstanding changes in u-boot-socfpga and u-boot-usb to > > >apply. I will, I've just been kicking builds on migrating > > >CONFIG_SPL_TEXT_BASE today, and I don't want to hold everything up on > > >being able to test those PRs. > > > > > >We're looking at release on April 8th, 2019. > > > > Is it still possible to include this fix in the upcoming release? > > > > [1] watchdog: Move watchdog_dev to data section (BSS may not be cleared) > > https://patchwork.ozlabs.org/patch/1075500/ > > I will give it a try, yes. I forgot to send the email, but I did apply it to the release. -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: