On Saturday 23 February 2008, Wolfgang Denk wrote:
In message 200802230359.32224.vapier@gentoo.org you wrote:
In message 200802230117.03679.vapier@gentoo.org you wrote:
Mike Frysinger (13): Blackfin: move bootldr command to common code Blackfin: convert BFIN_CPU to CONFIG_BFIN_CPU Blackfin: move on-chip MAC driver into drivers/net/ Blackfin: BF537-stamp: drop board-specific flash driver for CFI Blackfin: BF537-stamp: cleanup spi flash driver Blackfin: update MAINTAINERS list Blackfin: unify cpu and boot modes Blackfin: new cplbinfo command for viewing cplb tables Blackfin: add proper ELF markings to some assembly functions Blackfin: cleanup lib_blackfin/cache.c Blackfin: cleanup and overhaul common board init functions smc91111: use SSYNC() rather than asm(ssync) for Blackfin Blackfin: add error debug to serial driver
Hm... where are these changes coming from?
i'm in the process of merging the u-boot fork that we've been using at=20 blackfin.uclinux.org
I don't think any of them have been poosted on the mailing list before?
nope
Then that cannot go in now. We would break several rules at once: patches must be posted to the list first, and new stuff will get merged only when a merge window is open.
i understand where you're coming from, and i intend to follow the rules ... after Blackfin in mainline is actually usable. i'm being pragmatic here: since Blackfin literrally has never compiled/linked in the mainline releases, theres no way i could break it even more. delaying these updates to make mainline Blackfin u-boot usable is only that: delay.
as for posting the patches to the list, how do you know whether to merge it directly or pull from a repo ? -mike