Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Paul Sokolovsky <pmiscml@gmail.com>
To: Koen Kooi <koen@dominion.kabel.utwente.nl>
Cc: Using the OpenEmbedded metadata to build Linux Distributions
	<openembedded-devel@openembedded.org>
Subject: Re: [Openembedded-announce] kernel maintainers: COMPATIBLE_MACHINE field will become mandatory
Date: Thu, 12 Oct 2006 19:44:08 +0300	[thread overview]
Message-ID: <1167982954.20061012194408@gmail.com> (raw)
In-Reply-To: <452E0947.4070605@dominion.kabel.utwente.nl>

Hello Koen,

Thursday, October 12, 2006, 12:22:15 PM, you wrote:

[]

> Hi,

> At the OEDEM conference we decided that the COMPATIBLE_MACHINE field will be mandatory for
>  kernel recipes. If you maintain a kernel recipe: add the appropriate COMPATIBLE_MACHINE
> field. If you don't maintain a kernel recipe, but want to help: patches welcome.

> The COMPATIBLE_MACHINE machine field tells bitbake for which machines this is a valid
> kernel to avoid surprises for some reason the
> PREFERRED_PROVIDER_virtual/kernel gets broken.
> A lot of kernels already have that field, so have a look at first if you any questions.

  Just a question - should there be already machine conf file in OE
for anything added to COMPATIBLE_MACHINE, or can something be added as
an informative, "for-future", annotation?

> regards,

> Koen


-- 
Best regards,
 Paul                            mailto:pmiscml@gmail.com




  reply	other threads:[~2006-10-12 16:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-12  9:22 kernel maintainers: COMPATIBLE_MACHINE field will become mandatory Koen Kooi
2006-10-12 16:44 ` Paul Sokolovsky [this message]
2006-10-12 16:50   ` [Openembedded-devel] " Koen Kooi

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=1167982954.20061012194408@gmail.com \
    --to=pmiscml@gmail.com \
    --cc=koen@dominion.kabel.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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