Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1] Raspberry PI update
Date: Fri, 23 Sep 2016 07:58:27 +0200	[thread overview]
Message-ID: <20160923075827.341aeaec@free-electrons.com> (raw)
In-Reply-To: <1474580832-22406-1-git-send-email-ps.report@gmx.net>

Hello,

On Thu, 22 Sep 2016 23:47:06 +0200, Peter Seiderer wrote:

> Peter Seiderer (6):
>   raspberrypi0_defconfig: bump to kernel version 4.4.21
>   raspberrypi_defconfig: bump to kernel version 4.4.21
>   raspberrypi2_defconfig: bump to kernel version 4.4.21
>   raspberrypi3_defconfig: bump to kernel version 4.4.21
>   rpi-firmware: bump version
>   rpi-userland: bump version

I've applied to master, thanks for keeping those configurations updated.

However, next time, please generate your patches so that they contain
PATCH 1/N, PATCH 2/N, etc in their header.

Thanks again!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

      parent reply	other threads:[~2016-09-23  5:58 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 ` [Buildroot] [PATCH v1] raspberrypi0_defconfig: bump to kernel version 4.4.21 Peter Seiderer
2016-09-22 21:47 ` [Buildroot] [PATCH v1] raspberrypi_defconfig: " 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 ` Thomas Petazzoni [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=20160923075827.341aeaec@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