From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/linux-tools: fixes build of iio with 4.14+ kernels
Date: Tue, 12 Dec 2017 11:41:27 +0100 [thread overview]
Message-ID: <20171212114127.7969504d@windsurf> (raw)
In-Reply-To: <8efd7427-9096-bf58-0945-09e9fa3847a4@free.fr>
Hello,
On Tue, 12 Dec 2017 10:35:24 +0100, Julien Boibessot wrote:
> > Applied to master after improving the commit log. Thanks!
>
> Thanks Thomas, should I send the same for 2017.02 ?
Not needed, Peter will apply it to the 2017.02.x branch.
Ideally, when you know a patch is needed for 2017.02.x, it would be
nice to indicate that under the --- sign that follows the
Signed-off-by. This way, it is clear for Peter that the submitter wants
the patch in 2017.02.x.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-12-12 10:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 11:52 [Buildroot] [PATCH] package/linux-tools: fixes build of iio with 4.14+ kernels julien.boibessot at free.fr
2017-12-12 6:30 ` Thomas Petazzoni
2017-12-12 9:35 ` Julien Boibessot
2017-12-12 10:41 ` Thomas Petazzoni [this message]
2017-12-27 11:54 ` 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=20171212114127.7969504d@windsurf \
--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