From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/ltp-testsuite: update configure flags
Date: Wed, 18 Jan 2017 21:56:39 +1100 [thread overview]
Message-ID: <20170118215639.1378f596@free-electrons.com> (raw)
In-Reply-To: <20170118104427.g22n4od3usp4bpjh@dell5510>
Hello,
On Wed, 18 Jan 2017 11:44:28 +0100, Petr Vorel wrote:
> Not really (it applies to some releases before), but I can put it
> both into single commit, if you want.
No, if it's not related, then two separate patches like you did is
perfect. It's just that the commit log didn't make it completely clear.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-01-18 10:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 10:12 [Buildroot] [PATCH 1/2] package/ltp-testsuite: bump to version 20170116 Petr Vorel
2017-01-18 10:12 ` [Buildroot] [PATCH 2/2] package/ltp-testsuite: update configure flags Petr Vorel
2017-01-18 10:40 ` Thomas Petazzoni
2017-01-18 10:44 ` Petr Vorel
2017-01-18 10:56 ` Thomas Petazzoni [this message]
2017-01-20 3:09 ` [Buildroot] [PATCH 1/2] package/ltp-testsuite: bump to version 20170116 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=20170118215639.1378f596@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