All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ANN] U-Boot v2019.04-rc4 released
Date: Mon, 8 Apr 2019 09:09:59 -0400	[thread overview]
Message-ID: <20190408130959.GF4664@bill-the-cat> (raw)
In-Reply-To: <16184b24-9e7d-3df0-dc90-2016fb6b08fb@denx.de>

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.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190408/9627196a/attachment.sig>

  reply	other threads:[~2019-04-08 13:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-19  1:15 [U-Boot] [ANN] U-Boot v2019.04-rc4 released Tom Rini
2019-03-19  8:34 ` Anatolij Gustschin
2019-04-08 13:07 ` Stefan Roese
2019-04-08 13:09   ` Tom Rini [this message]
2019-04-09 11:58     ` Tom Rini
2019-04-09 11:59       ` Stefan Roese

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=20190408130959.GF4664@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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.