From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/4] linux: bump default to version 4.10
Date: Mon, 20 Feb 2017 21:58:05 +0100 [thread overview]
Message-ID: <20170220215805.219f3f32@free-electrons.com> (raw)
In-Reply-To: <1487591856-22997-1-git-send-email-festevam@gmail.com>
Hello,
On Mon, 20 Feb 2017 08:57:33 -0300, Fabio Estevam wrote:
> Signed-off-by: Fabio Estevam <festevam@gmail.com>
> ---
> Changes since v1:
> - None
I've applied all four patches to the next branch.
However, it would be useful if you could send patches for "next" based
on the current next branch. I had to fix a few (admittedly trivial)
conflicts when applying your patches, because you based them on master.
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2017-02-20 20:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 11:57 [Buildroot] [PATCH v2 1/4] linux: bump default to version 4.10 Fabio Estevam
2017-02-20 11:57 ` [Buildroot] [PATCH v2 2/4] toolchain: add 4.10.x choice for headers Fabio Estevam
2017-02-20 11:57 ` [Buildroot] [PATCH v2 3/4] linux-headers: bump to 4.10 kernel version Fabio Estevam
2017-02-20 11:57 ` [Buildroot] [PATCH v2 4/4] configs/mx6sx_udoo_neo: Bump to kernel 4.10 Fabio Estevam
2017-02-20 20: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=20170220215805.219f3f32@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