From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Marc Reilly <marc@cpdesign.com.au>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] arm: update mach-types
Date: Fri, 10 Dec 2010 09:20:20 +0100 [thread overview]
Message-ID: <20101210082020.GF19897@game.jcrosoft.org> (raw)
In-Reply-To: <201012101853.20192.marc@cpdesign.com.au>
On 18:53 Fri 10 Dec , Marc Reilly wrote:
> Hi,
>
> > PLwase specify against which kernel
> It's directly from http://www.arm.linux.org.uk/developer/machines/
>
> To be honest, I didn't even think about needing to match up against a specific
> version of the kernel, but I guess it does deserve consideration.
> From my understanding, the machine numbers are reserved forever and there is a
> 1:1 correspondence between the mach number and the device itself. It's only
> the label that may change. So this patch would be bad if someone has changed
> their machine name, but hasn't changed their code within barebox.
not really sometimes they change so to trac it it's better to have a reference
>
> I'll leave my thinking there because it's late friday arvo, and smarter minds
> have probably thought this one out before. :)
>
> Otherwise, would it be better if I just submitted a "one liner" patch which
> just adds my new machine?
no we update the whole file we need to be sync with the kernel
Best Regards,
J.
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2010-12-10 8:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 3:37 Marc Reilly
2010-12-10 6:43 ` Jean-Christophe PLAGNIOL-VILLARD
2010-12-10 7:53 ` Marc Reilly
2010-12-10 8:20 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2012-01-05 8:46 Juergen Kilb
2012-05-14 8:31 Jan Luebbe
2013-09-27 7:34 [PATCH] arm: Update mach-types Teresa Gámez
2013-09-27 8:57 ` Sascha Hauer
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=20101210082020.GF19897@game.jcrosoft.org \
--to=plagnioj@jcrosoft.com \
--cc=barebox@lists.infradead.org \
--cc=marc@cpdesign.com.au \
/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