On Wed, 2012-11-28 at 14:39 -0500, Peter Gavin wrote: > Hi guys, > > > I just cloned stefan's uClibc and linux repos into the github > openrisc. I just forked the uClibc repo Stefan had in his github, and > I cloned his repo at git://openrisc.net/stefan/linux onto my personal > github, then forked it from there.
You should probably ping the linux list ([email protected]) about this. The most up-to-date Linux should be upstream... if it's not, there's something wrong. Why aren't patches being submitted? Otherwise there's linux-next (also upstream-ish) which is perhaps even more up-to-date-ish, depending on how you see things. (And I do encourage people to run linux-next from time-to-time as it almost always contains stuff for openrisc that needs testing). My _only_ concern is that this becomes a dumping ground for stuff that won't be (or can't be) sent upstream; Linux patches need to go via the mailing list whence the road to the upstream kernel should be reasonably short (if not, just let me know where you think there's a problem and we'll see what we can do). NB, regarding uClibc, is that the repo you've cloned contains a set of patches that are incompatible with upstream... hopefully the whole uclibc/Linux syscall mess will be sorted out shortly. Otherwise, all good! Regards, Jonas _______________________________________________ OpenRISC mailing list [email protected] http://lists.openrisc.net/listinfo/openrisc
