Openembedded Core Discussions
 help / color / mirror / Atom feed
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 21:27:24 +0200	[thread overview]
Message-ID: <878f3830-3b43-cdd4-aa06-e237db4d0af0@linux.intel.com> (raw)
In-Reply-To: <233b2ff5-22a9-f378-98d9-fb833f5cc848@denx.de>

On 01/07/2018 07:55 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.
> 
> I guess the link in the xenomai recipe explains it, details are here:
> http://xenomai.org/installing-xenomai-3-x/

I need to clarify: all of these questions need to be answered in the 
context of oe-core. Essentially, you need to explain why the recipe 
should be in oe-core and not in its own layer.

>>> +SUMMARY = "Xenomai 3 userspace libraries"
>>> +DESCRIPTION = "Xenomai 3 userspace libraries"
>>
>> ... and here - description cannot be the same as the summary.
> 
> So do I remove one of them or what's the difference really ?

Same as the difference between commit summary and commit message. 
Description usually spans several lines, and provides fully formed 
sentences that explain what the software provided by the recipe does.

Also, an update to maintainers.inc would be appreciated, when adding new 
recipes.


Alex


  reply	other threads:[~2018-01-07 19:27 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 ` [PATCH 1/2] xenomai: Add xenomai recipe Alexander Kanavin
2018-01-07 17:55   ` Marek Vasut
2018-01-07 19:27     ` Alexander Kanavin [this message]
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=878f3830-3b43-cdd4-aa06-e237db4d0af0@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox