From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1] raspberrypi0_defconfig: bump to kernel version 4.4.21
Date: Thu, 22 Sep 2016 23:47:07 +0200 [thread overview]
Message-ID: <1474580832-22406-2-git-send-email-ps.report@gmx.net> (raw)
In-Reply-To: <1474580832-22406-1-git-send-email-ps.report@gmx.net>
Signed-off-by: Peter Seiderer <ps.report@gmx.net>
---
configs/raspberrypi0_defconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configs/raspberrypi0_defconfig b/configs/raspberrypi0_defconfig
index 87b1108..1ad56fe 100644
--- a/configs/raspberrypi0_defconfig
+++ b/configs/raspberrypi0_defconfig
@@ -10,7 +10,7 @@ BR2_TOOLCHAIN_BUILDROOT_CXX=y
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_GIT=y
BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://github.com/raspberrypi/linux.git"
-BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="26f3b72a9c049be10e6af196252283e1f6ab9d1f"
+BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="9669a50a3a8e4f33b4fe138277bc4407e1eab9b2"
BR2_LINUX_KERNEL_DEFCONFIG="bcmrpi"
# Build the DTBs for A/B from the kernel sources: the zero is the same
--
2.8.1
next prev parent reply other threads:[~2016-09-22 21:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 21:47 [Buildroot] [PATCH v1] Raspberry PI update Peter Seiderer
2016-09-22 21:47 ` Peter Seiderer [this message]
2016-09-22 21:47 ` [Buildroot] [PATCH v1] raspberrypi_defconfig: bump to kernel version 4.4.21 Peter Seiderer
2016-09-22 21:47 ` [Buildroot] [PATCH v1] raspberrypi2_defconfig: " Peter Seiderer
2016-09-22 21:47 ` [Buildroot] [PATCH v1] raspberrypi3_defconfig: " Peter Seiderer
2016-09-22 21:47 ` [Buildroot] [PATCH v1] rpi-firmware: bump version Peter Seiderer
2016-09-22 21:47 ` [Buildroot] [PATCH v1] rpi-userland: " Peter Seiderer
2016-09-23 5:58 ` [Buildroot] [PATCH v1] Raspberry PI update 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=1474580832-22406-2-git-send-email-ps.report@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