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’:
security/realcap.c
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
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
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 la
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 analyzed.
* 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
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 announc
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
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
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
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
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
12 matches
Mail list logo