On Thu, Jul 10, 2014 at 02:11:41PM +0200, Alexander Aring wrote: > Hi Martn, ... > > Normally it should into net, because it's a bugfix. But we can't do this > because so many things need to be changed and this occurs in a merge conflict, > then we put it in net-next. >
I was wrong here, net is for next kernel release net-next ist for next but one kernel release. If we want to fix something in stable we need to add the right CC: for stable mailinglist. I thought we get many merge conflicts because stable kernels. Nevertheless the current situation is that there are less people who working on non mainline kernel (always bleeding edge net-next or linux-wpan-next). This patch should based on "linux-wpan-next". In three years "maybe" we have some people who working on current mainline/stable kernels and then we should use "net/CC stable" for this. Then we can thinking about better stable strategies. - Alex ------------------------------------------------------------------------------ Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft _______________________________________________ Linux-zigbee-devel mailing list Linux-zigbee-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-zigbee-devel
