2.6.24-rc2-rt1 build failure: mod_unreg_security

2007-12-13 Thread Darren Hart
security/realcaps.c still uses mod_unreg_security and unregister_security to try and unregister the realtime capabilities from LSM. Those functions appear to have been removed from security/security.c, so the build fails with: security/realcap.c: In function ‘realtime_exit’:

2.6.24-rc2-rt1 build failure: mod_unreg_security

2007-12-13 Thread Darren Hart
security/realcaps.c still uses mod_unreg_security and unregister_security to try and unregister the realtime capabilities from LSM. Those functions appear to have been removed from security/security.c, so the build fails with: security/realcap.c: In function ‘realtime_exit’:

Re: [PATCH][RT] 2.6.24-rc2-rt1 drivers/dma/ioat_dma.c compile fix

2007-11-20 Thread trem
Steven Rostedt wrote: > On Fri, 16 Nov 2007, Nelson, Shannon wrote: >> first->async_tx.phys; >>> - __list_splice(_chain, ioat_chan->used_desc.prev); >>> + list_splice_tail(_chain, ioat_chan->used_desc.prev); >>> >> NAK. >> >> These functions do insertions differently. The 'prev' is

Re: [PATCH][RT] 2.6.24-rc2-rt1 drivers/dma/ioat_dma.c compile fix

2007-11-20 Thread trem
Steven Rostedt wrote: On Fri, 16 Nov 2007, Nelson, Shannon wrote: first-async_tx.phys; - __list_splice(new_chain, ioat_chan-used_desc.prev); + list_splice_tail(new_chain, ioat_chan-used_desc.prev); NAK. These functions do insertions differently. The 'prev' is pointing to the

Re: [PATCH][RT] 2.6.24-rc2-rt1 drivers/dma/ioat_dma.c compile fix

2007-11-16 Thread Nelson, Shannon
On Nov 16, 2007 3:57 AM, Sven-Thorsten Dietrich <[EMAIL PROTECTED]> wrote: > Compile fix for new code in -rc2. > > I'm not positive about the insertion point... > > Subject: compile error fix (needs review) > > RT changes __list_splice to require prev and next pointers. > > This changes the

Re: [PATCH][RT] 2.6.24-rc2-rt1 drivers/dma/ioat_dma.c compile fix

2007-11-16 Thread Steven Rostedt
On Fri, 16 Nov 2007, Nelson, Shannon wrote: > first->async_tx.phys; > > - __list_splice(_chain, ioat_chan->used_desc.prev); > > + list_splice_tail(_chain, ioat_chan->used_desc.prev); > > > > NAK. > > These functions do insertions differently. The 'prev' is pointing to > the last

[PATCH][RT] 2.6.24-rc2-rt1 drivers/dma/ioat_dma.c compile fix

2007-11-16 Thread Sven-Thorsten Dietrich
Compile fix for new code in -rc2. I'm not positive about the insertion point... Subject: compile error fix (needs review) RT changes __list_splice to require prev and next pointers. This changes the use in the new code to list_splice_tail, but the optimal insertion point needs to be

Re: [PATCH][RT] 2.6.24-rc2-rt1 drivers/dma/ioat_dma.c compile fix

2007-11-16 Thread Nelson, Shannon
On Nov 16, 2007 3:57 AM, Sven-Thorsten Dietrich [EMAIL PROTECTED] wrote: Compile fix for new code in -rc2. I'm not positive about the insertion point... Subject: compile error fix (needs review) RT changes __list_splice to require prev and next pointers. This changes the use in the

Re: [PATCH][RT] 2.6.24-rc2-rt1 drivers/dma/ioat_dma.c compile fix

2007-11-16 Thread Steven Rostedt
On Fri, 16 Nov 2007, Nelson, Shannon wrote: first-async_tx.phys; - __list_splice(new_chain, ioat_chan-used_desc.prev); + list_splice_tail(new_chain, ioat_chan-used_desc.prev); NAK. These functions do insertions differently. The 'prev' is pointing to the last valid

[PATCH][RT] 2.6.24-rc2-rt1 drivers/dma/ioat_dma.c compile fix

2007-11-16 Thread Sven-Thorsten Dietrich
Compile fix for new code in -rc2. I'm not positive about the insertion point... Subject: compile error fix (needs review) RT changes __list_splice to require prev and next pointers. This changes the use in the new code to list_splice_tail, but the optimal insertion point needs to be

Re: 2.6.24-rc2-rt1

2007-11-15 Thread Ingo Molnar
* Steven Rostedt <[EMAIL PROTECTED]> wrote: > Ingo, > > Do we still need to have the realtime-lsm.patch? It has been > considered obsolete for over a year now. Can we finally remove it. yeah, we can drop it. Ingo - To unsubscribe from this list: send the line "unsubscribe

Re: 2.6.24-rc2-rt1

2007-11-15 Thread Mark Knecht
On Nov 15, 2007 7:39 PM, Steven Rostedt <[EMAIL PROTECTED]> wrote: > > On Thu, 15 Nov 2007, Mark Knecht wrote: > > > > On Nov 15, 2007 10:40 AM, Steven Rostedt <[EMAIL PROTECTED]> wrote: > > > Finally! > > > > > > We are please

Re: 2.6.24-rc2-rt1

2007-11-15 Thread Steven Rostedt
On Thu, 15 Nov 2007, Mark Knecht wrote: > On Nov 15, 2007 10:40 AM, Steven Rostedt <[EMAIL PROTECTED]> wrote: > > Finally! > > > > We are pleased to announce 2.6.24-rc2-rt1. > > > > > Hi Steve, >Not sure I've ever posted on this list.

Re: 2.6.24-rc2-rt1

2007-11-15 Thread Steven Rostedt
On Thu, 15 Nov 2007, Mark Knecht wrote: > On Nov 15, 2007 10:40 AM, Steven Rostedt <[EMAIL PROTECTED]> wrote: > > Finally! > > > > We are pleased to announce 2.6.24-rc2-rt1. > > > > > Hi Steve, > >As always thanks the the rt-kernel team

Re: 2.6.24-rc2-rt1

2007-11-15 Thread Mark Knecht
Sent. On Nov 15, 2007 12:54 PM, Steven Rostedt <[EMAIL PROTECTED]> wrote: > > > On Thu, 15 Nov 2007, Mark Knecht wrote: > > > On Nov 15, 2007 10:40 AM, Steven Rostedt <[EMAIL PROTECTED]> wrote: > > > Finally! > > > > > > We are please

Re: 2.6.24-rc2-rt1

2007-11-15 Thread Mark Knecht
On Nov 15, 2007 10:40 AM, Steven Rostedt <[EMAIL PROTECTED]> wrote: > Finally! > > We are pleased to announce 2.6.24-rc2-rt1. > Hi Steve, Not sure I've ever posted on this list. Always looking to help out at my low level. Anyway, I tried building the kernel. My 1st

2.6.24-rc2-rt1

2007-11-15 Thread Steven Rostedt
Finally! We are pleased to announce 2.6.24-rc2-rt1. This is probably one of the toughest ports the -rt patch had to face. It was definitely the toughest one I had to perform. With a 50 Meg difference between 2.6.23 and 2.6.24-rc2 it caused a lot of problems with conflicts. The 2.6.23.1-rt11

2.6.24-rc2-rt1

2007-11-15 Thread Steven Rostedt
Finally! We are pleased to announce 2.6.24-rc2-rt1. This is probably one of the toughest ports the -rt patch had to face. It was definitely the toughest one I had to perform. With a 50 Meg difference between 2.6.23 and 2.6.24-rc2 it caused a lot of problems with conflicts. The 2.6.23.1-rt11

Re: 2.6.24-rc2-rt1

2007-11-15 Thread Mark Knecht
On Nov 15, 2007 10:40 AM, Steven Rostedt [EMAIL PROTECTED] wrote: Finally! We are pleased to announce 2.6.24-rc2-rt1. SNIP Hi Steve, Not sure I've ever posted on this list. Always looking to help out at my low level. Anyway, I tried building the kernel. My 1st two attempts, done

Re: 2.6.24-rc2-rt1

2007-11-15 Thread Mark Knecht
Sent. On Nov 15, 2007 12:54 PM, Steven Rostedt [EMAIL PROTECTED] wrote: On Thu, 15 Nov 2007, Mark Knecht wrote: On Nov 15, 2007 10:40 AM, Steven Rostedt [EMAIL PROTECTED] wrote: Finally! We are pleased to announce 2.6.24-rc2-rt1. SNIP Hi Steve, snip! As always

Re: 2.6.24-rc2-rt1

2007-11-15 Thread Steven Rostedt
On Thu, 15 Nov 2007, Mark Knecht wrote: On Nov 15, 2007 10:40 AM, Steven Rostedt [EMAIL PROTECTED] wrote: Finally! We are pleased to announce 2.6.24-rc2-rt1. SNIP Hi Steve, snip! As always thanks the the rt-kernel team for all you do. On behalf of the rt-kernel team, you

Re: 2.6.24-rc2-rt1

2007-11-15 Thread Steven Rostedt
On Thu, 15 Nov 2007, Mark Knecht wrote: On Nov 15, 2007 10:40 AM, Steven Rostedt [EMAIL PROTECTED] wrote: Finally! We are pleased to announce 2.6.24-rc2-rt1. SNIP Hi Steve, Not sure I've ever posted on this list. Always looking to help out at my low level. Anyway, I tried

Re: 2.6.24-rc2-rt1

2007-11-15 Thread Mark Knecht
On Nov 15, 2007 7:39 PM, Steven Rostedt [EMAIL PROTECTED] wrote: On Thu, 15 Nov 2007, Mark Knecht wrote: On Nov 15, 2007 10:40 AM, Steven Rostedt [EMAIL PROTECTED] wrote: Finally! We are pleased to announce 2.6.24-rc2-rt1. SNIP Hi Steve, Not sure I've ever posted

Re: 2.6.24-rc2-rt1

2007-11-15 Thread Ingo Molnar
* Steven Rostedt [EMAIL PROTECTED] wrote: Ingo, Do we still need to have the realtime-lsm.patch? It has been considered obsolete for over a year now. Can we finally remove it. yeah, we can drop it. Ingo - To unsubscribe from this list: send the line unsubscribe linux-kernel in