All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Esponde, Joel" <Joel.Esponde@Honeywell.com>
To: Bas Mevissen <abuse@basmevissen.nl>,
	"meta-freescale@yoctoproject.org"
	<meta-freescale@yoctoproject.org>
Subject: Re: imx-uuc: typo error
Date: Mon, 10 Apr 2017 11:05:09 +0000	[thread overview]
Message-ID: <MWHPR07MB344016E109BC5A1D394AD94496010@MWHPR07MB3440.namprd07.prod.outlook.com> (raw)
In-Reply-To: <7d6fdafe-a3b1-8cb6-0a5a-45ffffbeb8b4@basmevissen.nl>

> -----Message d'origine-----
> De : Bas Mevissen [mailto:abuse@basmevissen.nl]
> Envoyé : vendredi 7 avril 2017 16:24
> À : Esponde, Joel <Joel.Esponde@Honeywell.com>; meta-
> freescale@yoctoproject.org
> Objet : Re: [meta-freescale] imx-uuc: typo error
> 
> On 07/04/2017 11:53, Esponde, Joel wrote:
> >
> > For this kind of very small issue, is it sufficient to send just an
> > email like this?
> >
> > Or do I need to follow any patch based workflow?
> >
> >
> 
> This reminds me of an issue I ran into with the same package. It failed with
> QA issues:
> 
> ERROR: imx-uuc-0.5.1+gitAUTOINC+3440b11083-r1 do_package_qa: QA
> Issue:
> No GNU_HASH in the elf binary:
> '/work/build/tmp/work/bvd3_imx7d-poky-linux-gnueabi/imx-
> uuc/0.5.1+gitAUTOINC+3440b11083-r1/packages-split/imx-uuc/usr/bin/uuc'
> No GNU_HASH in the elf binary:
> '/work/build/tmp/work/bvd3_imx7d-poky-linux-gnueabi/imx-
> uuc/0.5.1+gitAUTOINC+3440b11083-r1/packages-split/imx-
> uuc/usr/bin/sdimage'
> [ldflags]
> 

Hi,

I did not see that issue on my side.
It built just fine.
Do you have an explanation on that?

Joël Esponde
Honeywell | Safety and Productivity Solutions



  parent reply	other threads:[~2017-04-10 12:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-07  9:53 imx-uuc: typo error Esponde, Joel
2017-04-07 14:23 ` Bas Mevissen
2017-04-07 20:14   ` Otavio Salvador
2017-04-10  9:27     ` Bas Mevissen
2017-04-10 11:06       ` Esponde, Joel
2017-04-10 14:01       ` Otavio Salvador
2017-08-16  6:41         ` Keskinarkaus, Teemu
2017-08-16 11:16           ` Bas Mevissen
2017-08-30 19:40             ` Otavio Salvador
2017-08-30 20:10               ` Bas Mevissen
2017-09-23 19:44               ` Bas Mevissen
2017-09-23 19:51                 ` Otavio Salvador
2017-04-10 11:05   ` Esponde, Joel [this message]
2017-04-10 11:57     ` Bas Mevissen
2017-04-10 14:09     ` Esponde, Joel
     [not found] <44f83cd2-a978-23f4-9337-8799bc8337a3@yahoo.it>
2017-10-03  7:24 ` Gianfranco Costamagna

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=MWHPR07MB344016E109BC5A1D394AD94496010@MWHPR07MB3440.namprd07.prod.outlook.com \
    --to=joel.esponde@honeywell.com \
    --cc=abuse@basmevissen.nl \
    --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.