Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 0/5] Raspberry Pi update
Date: Mon, 15 Oct 2018 13:17:21 +0200	[thread overview]
Message-ID: <87in23o3we.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20181012210941.21515-1-ps.report@gmx.net> (Peter Seiderer's message of "Fri, 12 Oct 2018 23:09:36 +0200")

>>>>> "Peter" == Peter Seiderer <ps.report@gmx.net> writes:

 > Update configs/raspberrypi*, rpi-firmware, rpi-userland, rpi-bt-firmware
 > and rpi-wifi-firmware to latest versions.

 > Tested on Raspberry Pi 3 Model B v1.2 hardware:
 > - raspberrypi3_defconfig updated to glibc, systemd, gcc-8.x and
 >   qt5 (linuxfb, eglfs)


 > Peter Seiderer (5):
 >   configs/raspberrypi*: bump kernel version to 6d27aa156c
 >   rpi-firmware: bump version to fbad6408c4
 >   rpi-userland: bump version to 8f0abfb07b
 >   rpi-bt-firmware: bump version to 8c1e2bff1d
 >   rpi-wifi-firmware: bump version to 8c1e2bff1d

Committed series, thanks.

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2018-10-15 11:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-12 21:09 [Buildroot] [PATCH v1 0/5] Raspberry Pi update Peter Seiderer
2018-10-12 21:09 ` [Buildroot] [PATCH v1 1/5] configs/raspberrypi*: bump kernel version to 6d27aa156c Peter Seiderer
2018-10-12 21:09 ` [Buildroot] [PATCH v1 2/5] rpi-firmware: bump version to fbad6408c4 Peter Seiderer
2018-10-15 11:18   ` Peter Korsgaard
2018-11-04 21:37     ` Peter Seiderer
2018-10-12 21:09 ` [Buildroot] [PATCH v1 3/5] rpi-userland: bump version to 8f0abfb07b Peter Seiderer
2018-10-12 21:09 ` [Buildroot] [PATCH v1 4/5] rpi-bt-firmware: bump version to 8c1e2bff1d Peter Seiderer
2018-10-12 21:09 ` [Buildroot] [PATCH v1 5/5] rpi-wifi-firmware: " Peter Seiderer
2018-10-15 11:17 ` Peter Korsgaard [this message]

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=87in23o3we.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --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