From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Marek Vasut <marex@denx.de>, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] xenomai: Add xenomai recipe
Date: Sun, 7 Jan 2018 19:17:07 +0200 [thread overview]
Message-ID: <3cdba2e1-94df-32fd-0138-a6fa533ec165@linux.intel.com> (raw)
In-Reply-To: <20180107161920.30937-1-marex@denx.de>
On 01/07/2018 06:19 PM, Marek Vasut wrote:
> Add recipe for the xenomai. This recipe is used twice, once to build
> the xenomai userspace components and again to patch the kernel with
> the cobalt core. Therefore, the xenomai sources are installed into
> work-shared rather then work to make them accessible to the kernel
> recipe, which triggers the patching.
What is xenomai? What is a 'cobalt core'? What do they do and who would
want to use them? Please do explain that in the commit message.
> +SUMMARY = "Xenomai 3 userspace libraries"
> +DESCRIPTION = "Xenomai 3 userspace libraries"
... and here - description cannot be the same as the summary.
Alex
next prev parent reply other threads:[~2018-01-07 17:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-07 16:19 [PATCH 1/2] xenomai: Add xenomai recipe Marek Vasut
2018-01-07 16:19 ` [PATCH 2/2] kernel: Add optional patch_xenomai task Marek Vasut
2018-01-07 16:37 ` Bruce Ashfield
2018-01-07 16:38 ` Marek Vasut
2018-01-07 16:42 ` Bruce Ashfield
2018-01-07 16:51 ` Bruce Ashfield
2018-01-07 17:53 ` Marek Vasut
2018-01-07 17:55 ` Bruce Ashfield
2018-01-07 18:49 ` Marek Vasut
2018-01-07 18:55 ` Bruce Ashfield
2018-01-07 18:57 ` Marek Vasut
2018-01-07 19:00 ` Bruce Ashfield
2018-01-07 19:38 ` Marek Vasut
2018-01-08 1:32 ` akuster808
2018-01-07 17:17 ` Alexander Kanavin [this message]
2018-01-07 17:55 ` [PATCH 1/2] xenomai: Add xenomai recipe Marek Vasut
2018-01-07 19:27 ` Alexander Kanavin
2018-01-07 19:37 ` Marek Vasut
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=3cdba2e1-94df-32fd-0138-a6fa533ec165@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=marex@denx.de \
--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 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.