Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Bas Mevissen <abuse@basmevissen.nl>,
	Openembedded Core <openembedded-core@lists.openembedded.org>
Subject: Re: Summary of kernel-devsrc package issues (Sumo)
Date: Mon, 4 Jun 2018 14:32:10 +0300	[thread overview]
Message-ID: <0c5a1317-bbed-4de5-d0d7-d34989d53e7e@linux.intel.com> (raw)
In-Reply-To: <be75fca2a4a635993bfaf89073fc0bd3@basmevissen.nl>

On 06/04/2018 12:04 PM, Bas Mevissen wrote:
> I ran into several issues with kernel-devsrc when building Poky Sumu 
> with the meta-freescale layer for an Freescale i.mx6sx ARM board. In 
> this mail(thread) I would like to collect them all and discuss the 
> possible options to resolve them.

This is probably better discussed here:
https://lists.yoctoproject.org/listinfo/linux-yocto

Alex



  reply	other threads:[~2018-06-04 11:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-04  9:04 Summary of kernel-devsrc package issues (Sumo) Bas Mevissen
2018-06-04 11:32 ` Alexander Kanavin [this message]
2018-06-04 13:23   ` Bas Mevissen
2018-06-04 12:32 ` Bruce Ashfield
2018-06-04 13:35   ` Bas Mevissen

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=0c5a1317-bbed-4de5-d0d7-d34989d53e7e@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=abuse@basmevissen.nl \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox