From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/rpi-firmware: bump version to 83977fe3b6
Date: Sat, 23 Feb 2019 15:27:11 +0100 [thread overview]
Message-ID: <20190223152711.6caac341@gmx.net> (raw)
In-Reply-To: <20190223143753.59fcb120@windsurf.home>
Hello Thomas,
On Sat, 23 Feb 2019 14:37:53 +0100, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> On Fri, 22 Feb 2019 23:37:04 +0100
> Peter Seiderer <ps.report@gmx.net> wrote:
>
> > Signed-off-by: Peter Seiderer <ps.report@gmx.net>
>
> What is the reason for bumping to 83977fe3b6 in master ? And then to
> ebf7b40cdc in next ?
Sorry for the confusion, preparing the bump (maybe buildroot-master) to
- kernel 877656cd14 (4.14.98, up-to-date one from the 4.14 branch)
- firmware 83977fe3b6, last commit before [1]:
kernel bump to 4.19.23
See: https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=224931
overlapped with the release of 4.19.23 [3] and the follow up bump (major kernel
update for buildroot-next) to
- kernel 5eeff139ea (4.19.23)
- firmware ebf7b40cdc [2], one commit after [1],
Regards,
Peter
[1] https://github.com/raspberrypi/firmware/commit/d095b96ac33de9eb4b95539cb3261f35a3c74509
[2] https://github.com/raspberrypi/firmware/commit/ebf7b40cdc6effe7ffa3fd5195e8be01b94f80da
[3] https://www.phoronix.com/scan.php?page=news_item&px=Raspberry-Pi-Linux-4.19-Rolling
>
> Thomas
next prev parent reply other threads:[~2019-02-23 14:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 22:37 [Buildroot] [PATCH 1/2] configs/raspberrypi*: bump kernel version to 877656cd14 Peter Seiderer
2019-02-22 22:37 ` [Buildroot] [PATCH 2/2] package/rpi-firmware: bump version to 83977fe3b6 Peter Seiderer
2019-02-23 13:37 ` Thomas Petazzoni
2019-02-23 14:27 ` Peter Seiderer [this message]
2019-02-23 14:54 ` Thomas Petazzoni
2019-02-23 22:09 ` Peter Seiderer
2019-04-16 20:42 ` [Buildroot] [PATCH 1/2] configs/raspberrypi*: bump kernel version to 877656cd14 Thomas Petazzoni
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=20190223152711.6caac341@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox