Dear Tom,
In message 20140707161204.GM29202@bill-the-cat you wrote:
You can either fetch the Linux tree into your local U-Boot repo (or vice versa) so that git diff can compare them, or you can check out separate repositories to the proper tags/SHAs and use ordinary diff. It's not something that I'd expect one to want to do very often, though. Usually you want to know how things work in the codebase you're working on, or you want to compare some specific aspect of the code which can more easily be done manually.
So an example of this would be doing say: $ git diff 3dad234 drivers/mtd/nand/nand_base.c
Yes - but this works only on a per-file or per-directory base. As I mentioned before, the code is scattered over a number of directories (and I'm not even sure that we don't have any renames to deal with).
Where 3dad234 is the last kernel commit to U-Boot drivers/mtd/nand/nand_base.c where we synced right (and we've fetched the kernel sources into this repo as well) ? (This commit is also valid for atmel_nand.c and I looked over the results there too..).
As Heiko explains in his posting, his patches are agains kernel tag v3.14 = commit ID 455c6fd
We must, really, follow the general rule where when we sync stuff from the kernel we say what the commit we synced with is, for UBI/etc. We may not have been for forever but the last time we also said that tag it was against.
Heiko included this information in his posting.
In sum, if Heiko is going to be owning UBI/related code and syncs, whatever makes life easiest on _him_ to make sure we don't have regressions is fine with me (within reason, and this seems to be within reason). Do not get me wrong please, I appreciate all the time you've spent thus far in U-Boot and wish and want you to comment / review / advise as you're still able to find time. But if someone else is taking up doing the re-syncs it needs to also fit their workflow.
Thanks. Well, officially UBI is in the responsibility of Kyungmin Park (though Stefan Roese did a major part of that work, too), and MTD is something we haven't defined yet. But I think Heiko will watch over this area and care about any upcoing issues related to this update at least for the next weeks and months...
Best regards,
Wolfgang Denk