From: Saul Wold <sgw@linux.intel.com>
To: Otavio Salvador <otavio@ossystems.com.br>,
OpenEmbedded Core Mailing List
<openembedded-core@lists.openembedded.org>
Subject: Re: [daisy-backport][PATCH 0/6] Daisy backports
Date: Thu, 22 May 2014 11:47:43 -0700 [thread overview]
Message-ID: <537E464F.10700@linux.intel.com> (raw)
In-Reply-To: <1400783274-7258-1-git-send-email-otavio@ossystems.com.br>
On 05/22/2014 11:27 AM, Otavio Salvador wrote:
> Hello,
>
> Those are the changes I have in my local backport branch which I run
> on top of 'sgw/daisy' branch.
>
> Chen Qi (2):
> tcf-agent: add systemd support
> gdb: add PACKAGECONFIG for babeltrace
>
These are already in my branch
> Denys Dmytriyenko (3):
> cryptodev-linux: move to recipes-kernel to be shared with module and
> tests
> cryptodev-linux: create common .inc file to be shared by module and
> tests
> cryptodev-tests: recipe for cryptodev test suite based on OpenSSL
>
I have pulled these for testing, but we don't normally enable new
functionality in point releases. I would like to get a clear
justification as to why these are needed to be back-ported.
Please provide more details on the cryptodev functionality and why it
should be backported.
Thanks
Sau!
> Tudor Florea (1):
> curl: remove inapporpriate file from curl release
>
> .../openssl/cryptodev-linux_1.6.bb | 22 -
> meta/recipes-devtools/gdb/gdb_7.6.2.bb | 1 +
> .../tcf-agent/tcf-agent/tcf-agent.service | 10 +
> meta/recipes-devtools/tcf-agent/tcf-agent_git.bb | 8 +-
> .../cryptodev/cryptodev-linux_1.6.bb | 15 +
> .../cryptodev/cryptodev-tests_1.6.bb | 23 +
> meta/recipes-kernel/cryptodev/cryptodev_1.6.inc | 11 +
> ...pile-and-install-rules-for-cryptodev-test.patch | 69 +
> ...ests-Makefile-usage-of-LDLIBS-vs.-LDFLAGS.patch | 29 +
> .../curl/remove_inappropriate_file_from_rel.patch | 8203 ++++++++++++++++++++
> meta/recipes-support/curl/curl_7.35.0.bb | 1 +
> 11 files changed, 8369 insertions(+), 23 deletions(-)
> delete mode 100644 meta/recipes-connectivity/openssl/cryptodev-linux_1.6.bb
> create mode 100644 meta/recipes-devtools/tcf-agent/tcf-agent/tcf-agent.service
> create mode 100644 meta/recipes-kernel/cryptodev/cryptodev-linux_1.6.bb
> create mode 100644 meta/recipes-kernel/cryptodev/cryptodev-tests_1.6.bb
> create mode 100644 meta/recipes-kernel/cryptodev/cryptodev_1.6.inc
> create mode 100644 meta/recipes-kernel/cryptodev/files/0001-Add-the-compile-and-install-rules-for-cryptodev-test.patch
> create mode 100644 meta/recipes-kernel/cryptodev/files/0002-Fix-tests-Makefile-usage-of-LDLIBS-vs.-LDFLAGS.patch
> create mode 100644 meta/recipes-support/curl/curl/remove_inappropriate_file_from_rel.patch
>
next prev parent reply other threads:[~2014-05-22 18:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 18:27 [daisy-backport][PATCH 0/6] Daisy backports Otavio Salvador
2014-05-22 18:27 ` [daisy-backport][PATCH 1/6] tcf-agent: add systemd support Otavio Salvador
2014-05-22 18:27 ` [daisy-backport][PATCH 2/6] cryptodev-linux: move to recipes-kernel to be shared with module and tests Otavio Salvador
2014-05-22 18:27 ` [daisy-backport][PATCH 3/6] cryptodev-linux: create common .inc file to be shared by " Otavio Salvador
2014-05-22 18:27 ` [daisy-backport][PATCH 4/6] cryptodev-tests: recipe for cryptodev test suite based on OpenSSL Otavio Salvador
2014-05-22 18:27 ` [daisy-backport][PATCH 5/6] curl: remove inapporpriate file from curl release Otavio Salvador
2014-05-22 18:27 ` [daisy-backport][PATCH 6/6] gdb: add PACKAGECONFIG for babeltrace Otavio Salvador
2014-05-22 18:47 ` Saul Wold [this message]
2014-05-22 18:56 ` [daisy-backport][PATCH 0/6] Daisy backports Otavio Salvador
2014-05-22 19:09 ` Denys Dmytriyenko
2014-05-22 19:15 ` Otavio Salvador
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=537E464F.10700@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.