All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Patrick Ohly <patrick.ohly@intel.com>
Cc: openembedded-devel <openembedded-devel@lists.openembedded.org>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: State of bitbake world 2016-06-13
Date: Wed, 15 Jun 2016 17:29:16 +0200	[thread overview]
Message-ID: <CA+chaQc-WwdLz78kLJhSPxo3UrfN8TD7VYaVvxvf=Xwq+EJiyQ@mail.gmail.com> (raw)
In-Reply-To: <1466002419.9543.1.camel@intel.com>

[-- Attachment #1: Type: text/plain, Size: 655 bytes --]

Derek already sent similar patches.

Thanks

On Wed, Jun 15, 2016 at 4:53 PM, Patrick Ohly <patrick.ohly@intel.com>
wrote:

> On Wed, 2016-06-15 at 12:45 +0200, Martin Jansa wrote:
> > libgphoto2, v4l-utils fail because recent upgrade of libjpeg-turbo in
> oe-core (PNBLACKLIST sent)
>
> I have patches ready for that, will send them now.
>
> --
> Best Regards, Patrick Ohly
>
> The content of this message is my personal opinion only and although
> I am an employee of Intel, the statements I make here in no way
> represent Intel's position on the issue, nor am I authorized to speak
> on behalf of Intel on this matter.
>
>
>
>

[-- Attachment #2: Type: text/html, Size: 1085 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Martin Jansa <martin.jansa@gmail.com>
To: Patrick Ohly <patrick.ohly@intel.com>
Cc: openembedded-devel <openembedded-devel@lists.openembedded.org>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] State of bitbake world 2016-06-13
Date: Wed, 15 Jun 2016 17:29:16 +0200	[thread overview]
Message-ID: <CA+chaQc-WwdLz78kLJhSPxo3UrfN8TD7VYaVvxvf=Xwq+EJiyQ@mail.gmail.com> (raw)
In-Reply-To: <1466002419.9543.1.camel@intel.com>

Derek already sent similar patches.

Thanks

On Wed, Jun 15, 2016 at 4:53 PM, Patrick Ohly <patrick.ohly@intel.com>
wrote:

> On Wed, 2016-06-15 at 12:45 +0200, Martin Jansa wrote:
> > libgphoto2, v4l-utils fail because recent upgrade of libjpeg-turbo in
> oe-core (PNBLACKLIST sent)
>
> I have patches ready for that, will send them now.
>
> --
> Best Regards, Patrick Ohly
>
> The content of this message is my personal opinion only and although
> I am an employee of Intel, the statements I make here in no way
> represent Intel's position on the issue, nor am I authorized to speak
> on behalf of Intel on this matter.
>
>
>
>


  parent reply	other threads:[~2016-06-15 15:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-15 10:45 State of bitbake world 2016-06-13 Martin Jansa
2016-06-15 14:53 ` Patrick Ohly
2016-06-15 15:08   ` [meta-oe][PATCH 1/2] libgphoto2: fix compatibility with libjpeg-turbo Patrick Ohly
2016-06-15 15:08     ` [meta-oe][PATCH 2/2] v4l-utils: " Patrick Ohly
2016-06-16  9:09     ` [meta-oe][PATCH 1/2] libgphoto2: " Patrick Ohly
2016-06-15 15:29   ` Martin Jansa [this message]
2016-06-15 15:29     ` [OE-core] State of bitbake world 2016-06-13 Martin Jansa
  -- strict thread matches above, loose matches on Subject: below --
2016-06-13 20:01 Martin Jansa

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='CA+chaQc-WwdLz78kLJhSPxo3UrfN8TD7VYaVvxvf=Xwq+EJiyQ@mail.gmail.com' \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=patrick.ohly@intel.com \
    /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.