All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Cochran <yocto@mindchasers.com>
To: meta-freescale@yoctoproject.org
Subject: Re: [PATCH 0/2] cryptodev-fsl/openssl: add missing colon for FILESEXTRAPATHS
Date: Tue, 22 Jul 2014 23:53:40 -0400	[thread overview]
Message-ID: <53CF31C4.10308@mindchasers.com> (raw)
In-Reply-To: <cover.1406086040.git.hongxu.jia@windriver.com>

Just pointing out that it would save time to mention up front that these 
are for the meta-fsl-ppc repo (assuming I'm not mistaken) and not the 
iMX FSL repos.

Freescale developers have been patching meta-fsl-ppc recently and 
[meta-fsl-ppc] has been included in the email subject line, which helps 
a great deal when scanning through a lot of emails.



On 07/22/2014 11:30 PM, Hongxu Jia wrote:
> The following changes since commit 0772054526043a29b73345540174f2c344f9a353:
>
>    ipc-modules: move to recipes-kernel/ (2014-07-15 14:13:21 +0800)
>
> are available in the git repository at:
>
>    git://git.pokylinux.org/poky-contrib hongxu/freescale
>    http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=hongxu/freescale
>
> Hongxu Jia (2):
>    cryptodev-fsl: add missing colon for FILESEXTRAPATHS
>    openssl_1.0.1g.bbappend: add missing colon for FILESEXTRAPATHS
>
>   recipes-connectivity/openssl/openssl_1.0.1g.bbappend | 2 +-
>   recipes-kernel/cryptodev/cryptodev-fsl.inc           | 2 +-
>   2 files changed, 2 insertions(+), 2 deletions(-)
>



  parent reply	other threads:[~2014-07-23  3:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-23  3:30 [PATCH 0/2] cryptodev-fsl/openssl: add missing colon for FILESEXTRAPATHS Hongxu Jia
2014-07-23  3:30 ` [PATCH 1/2] cryptodev-fsl: " Hongxu Jia
2014-07-23  3:30 ` [PATCH 2/2] openssl_1.0.1g.bbappend: " Hongxu Jia
2014-07-23  3:53 ` Bob Cochran [this message]
2014-07-23  4:28   ` [meta-fsl-ppc] [PATCH 0/2] cryptodev-fsl/openssl: " Hongxu Jia
2014-07-25  8:17 ` Hongxu Jia
2014-07-25  8:20   ` Hongxu Jia

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=53CF31C4.10308@mindchasers.com \
    --to=yocto@mindchasers.com \
    --cc=meta-freescale@yoctoproject.org \
    /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.