No. This will quicklly result in a maze of merge conflicts.
We will always only update the file as a whole. THe only option I'm willing to discuss is where to get the file from.
One catch remains, of course: I someone changed their entry at the
database,
compilation of u-boot for that board could break. I think that entries
that
have propagated to the mainline Linux kernel cannot be changed anymore.
Right. Which is exactly the reason for syncing against this version.
I'd also think the u-boot mach-type.h could do well without all the
function
definitions. I have not grepped, however, if someone in u-boot uses them.
I don;t think we do. But as mentioned above, we don;t want to mess with this file, we just update it as is.
Best regards,
Wolfgang Denk
We are in sync with the latest in linux kernel
Take a look at
http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=history;f=ar...
Regards, Sandeep