search for: besed

Hi, I split the previous support security EA patch into four patches for review. Them besed on joel's xattr-28 branch and tao's patch "Merge xattr set transaction". 1: move new_inode out of the transaction. 2: add ocfs2_xattr_set_handle. 3: add security xattr APIs 4: add init_security in mknod. Best regards, tiger

...3.4.2 and so on), but ONLY shortly before he opens the "rc" pull window for his next release series (here: 3.5-rc1). So it indeed looks as if all the local commits on the nouveau git have been made on a 3.4.0 kernel, although they ended up in the official 3.5 version released by Linus. Besed on this, I did further testing: Both "5e120f6e4b3f35b741c5445dfc755f50128c3c44^" and "5e120f6e4b3f35b741c5445dfc755f50128c3c44" do still run fine, i.e. the commit 5e120f6e4b3f35b741c5445dfc755f50128c3c44 - which actually introduced the nv84_fence - does NOT seem to be causing t...

...his next release series (here: > 3.5-rc1). That would be one possible moment where the conditions are ideal enough to pull. Though I am in doubt whether it matters when this was pulled from Linus. If you don't like to bisect the Nouveau development branch, you can bisect kernel git. > Besed on this, I did further testing: > > Both "5e120f6e4b3f35b741c5445dfc755f50128c3c44^" and > "5e120f6e4b3f35b741c5445dfc755f50128c3c44" do still run fine, i.e. the > commit 5e120f6e4b3f35b741c5445dfc755f50128c3c44 - which actually introduced > the nv84_fence - does...

I've taken the liberty of starting a new thread to discuss the design of the Asterisk CDR mechanism. The discussion has been kindly initiated by murf putting together a proposal: http://svn.digium.com/svn/asterisk/team/murf/RFCs. After reading the proposal I still don't think it's the right way to go. To my mind adding more channel variables increases the complexity in a situation