From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] bluez5_utils: new package
Date: Mon, 23 Dec 2013 10:50:59 +0100 [thread overview]
Message-ID: <20131223105059.26698156@skate> (raw)
In-Reply-To: <1387791444-28056-1-git-send-email-alexandre.belloni@free-electrons.com>
Dear Alexandre Belloni,
On Mon, 23 Dec 2013 10:37:24 +0100, Alexandre Belloni wrote:
> Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
> ---
> package/Config.in | 1 +
> package/bluez5_utils/Config.in | 16 ++++
> .../bluez5_utils-5.12-enable_cg2900.patch | 106 +++++++++++++++++++++
> package/bluez5_utils/bluez5_utils.mk | 31 ++++++
> package/bluez_utils/Config.in | 8 +-
> 5 files changed, 161 insertions(+), 1 deletion(-)
> create mode 100644 package/bluez5_utils/Config.in
> create mode 100644 package/bluez5_utils/bluez5_utils-5.12-enable_cg2900.patch
> create mode 100644 package/bluez5_utils/bluez5_utils.mk
When you send a new version of a patch, please change the subject
prefix to add "PATCH v2", and also include a changelog in your patch so
that we know what changed between v1 and v2.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-12-23 9:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-23 9:37 [Buildroot] [PATCH] bluez5_utils: new package Alexandre Belloni
2013-12-23 9:50 ` Baruch Siach
2013-12-23 9:54 ` Alexandre Belloni
2013-12-23 9:57 ` Baruch Siach
2013-12-23 10:11 ` Thomas Petazzoni
2013-12-23 10:16 ` Alexandre Belloni
2013-12-23 10:17 ` Baruch Siach
2013-12-23 9:50 ` Thomas Petazzoni [this message]
2013-12-23 9:57 ` Thomas Petazzoni
2014-03-07 22:56 ` Thomas Petazzoni
2014-03-07 23:03 ` Alexandre Belloni
2014-03-07 23:09 ` Thomas Petazzoni
-- strict thread matches above, loose matches on Subject: below --
2013-11-04 12:59 Marcin Bis
2013-11-04 16:06 ` Thomas De Schampheleire
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=20131223105059.26698156@skate \
--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