From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 0/6] Raspberry PI update
Date: Sun, 4 Dec 2016 15:59:55 +0100 [thread overview]
Message-ID: <20161204155955.1c7be41a@free-electrons.com> (raw)
In-Reply-To: <20161203231137.32221-1-ps.report@gmx.net>
Hello,
On Sun, 4 Dec 2016 00:11:31 +0100, Peter Seiderer wrote:
> Peter Seiderer (6):
> raspberrypi0_defconfig: bump kernel version to 4.4.36
> raspberrypi_defconfig: bump kernel version to 4.4.36
> raspberrypi2_defconfig: bump kernel version to 4.4.36
> raspberrypi3_defconfig: bump kernel version to 4.4.36
> rpi-firmware: bump version
> rpi-userland: bump version
All applied, thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-12-04 14:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-03 23:11 [Buildroot] [PATCH v1 0/6] Raspberry PI update Peter Seiderer
2016-12-03 23:11 ` [Buildroot] [PATCH v1 1/6] raspberrypi0_defconfig: bump kernel version to 4.4.36 Peter Seiderer
2016-12-03 23:11 ` [Buildroot] [PATCH v1 2/6] raspberrypi_defconfig: " Peter Seiderer
2016-12-03 23:11 ` [Buildroot] [PATCH v1 3/6] raspberrypi2_defconfig: " Peter Seiderer
2016-12-03 23:11 ` [Buildroot] [PATCH v1 4/6] raspberrypi3_defconfig: " Peter Seiderer
2016-12-03 23:11 ` [Buildroot] [PATCH v1 5/6] rpi-firmware: bump version Peter Seiderer
2016-12-03 23:11 ` [Buildroot] [PATCH v1 6/6] rpi-userland: " Peter Seiderer
2016-12-04 14:59 ` Thomas Petazzoni [this message]
[not found] <FbC91u0112zVPbg01bCA0v>
[not found] ` <35324051-2281-6578-68fb-28ddf3e744bd@cox.net>
2016-12-04 14:21 ` [Buildroot] [PATCH v1 0/6] Raspberry PI update Peter Seiderer
-- strict thread matches above, loose matches on Subject: below --
2017-01-23 20:23 [Buildroot] [PATCH v1 0/6] Raspberry Pi update Peter Seiderer
2017-01-23 22:01 ` Peter Korsgaard
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=20161204155955.1c7be41a@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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