From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] bluez5_utils: fix big endian build
Date: Sun, 28 Feb 2016 23:08:21 +0100 [thread overview]
Message-ID: <20160228230821.47820f15@free-electrons.com> (raw)
In-Reply-To: <1456489054-10492-1-git-send-email-john@keeping.me.uk>
Dear John Keeping,
On Fri, 26 Feb 2016 12:17:34 +0000, John Keeping wrote:
> From: John Keeping <john@metanate.com>
>
> This patch has been accepted upstream and requires no changes to apply
> to 5.37.
>
> Signed-off-by: John Keeping <john@metanate.com>
> ---
> I'm not sure whether an S-o-b should be applied to the patch in this
> commit; the upstream bluez project does not accept patches with an S-o-b
> and the patch included here is the unmodified output of:
I've applied to master, with the following changes:
[Thomas:
- add reference to upstream commit
- add John's SoB to the patch itself
- add reference to autobuilder failure.]
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-02-28 22:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 12:17 [Buildroot] [PATCH] bluez5_utils: fix big endian build John Keeping
2016-02-26 12:31 ` Baruch Siach
2016-02-28 22:08 ` 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=20160228230821.47820f15@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