From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] Fetch machine type list for ARM architectures
Date: Thu, 17 Sep 2009 09:36:25 +0200 [thread overview]
Message-ID: <h8sotp$hld$1@ger.gmane.org> (raw)
In-Reply-To: <c384c5ea0909161456r48c25a89n5d3e902e2f98b089@mail.gmail.com>
On 16-09-09 23:56, Leon Woestenberg wrote:
> Hello,
>
> two (known) ARM machines currently have kernel support but their
> "mach-types" file in arch/arm/tools/ is not up-to-date.
>
> I had this change in my local tree. It works, but is quite intrusive
> as it is mixing a well-known version of the kernel sources (as per the
> recipe) against an upstream, constantly changing file.
> This is unwanted.
>
> I rather think we should fetch the mach-types file only for those
> machine that require it.
And not do this for machines that have a different machine number than
Russel think (the joy of nonstandard bootloaders).
regards,
Koen
prev parent reply other threads:[~2009-09-17 7:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 21:56 [RFC] Fetch machine type list for ARM architectures Leon Woestenberg
2009-09-17 7:33 ` Phil Blundell
2009-09-25 9:26 ` Leon Woestenberg
2009-09-17 7:36 ` Koen Kooi [this message]
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='h8sotp$hld$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@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