Hi,
On my i386 machine I can't compile. I have an error in net/ipv6/mcast.c
I correct the error doing the correction below. No more compilation problem.
Not yet tested. perhaps someone already submit it, but I received no mail today from vger.kernel.org
Index: linux/net/ipv6/mcast.c
===================================================================
--- linux.orig/net/ipv6/mcast.c
+++ linux/net/ipv6/mcast.c
@@ -224,7 +224,7 @@
mc_lst->ifindex = dev->ifindex;
mc_lst->sfmode = MCAST_EXCLUDE;
- mc_lst->sflock = RW_LOCK_UNLOCKED;
+ mc_lst->sflock = RW_LOCK_UNLOCKED(mc_lst->sflock);
mc_lst->sflist = NULL;
/*
I thought I submitted an identical patch, but maybe I forgot to CC LKML .
On Wed, 4 Jan 2006, Serge Noiraud wrote:
> Hi,
>
> On my i386 machine I can't compile. I have an error in net/ipv6/mcast.c
> I correct the error doing the correction below. No more compilation problem.
> Not yet tested. perhaps someone already submit it, but I received no mail today from vger.kernel.org
>
> Index: linux/net/ipv6/mcast.c
> ===================================================================
> --- linux.orig/net/ipv6/mcast.c
> +++ linux/net/ipv6/mcast.c
> @@ -224,7 +224,7 @@
>
> mc_lst->ifindex = dev->ifindex;
> mc_lst->sfmode = MCAST_EXCLUDE;
> - mc_lst->sflock = RW_LOCK_UNLOCKED;
> + mc_lst->sflock = RW_LOCK_UNLOCKED(mc_lst->sflock);
> mc_lst->sflist = NULL;
>
> /*
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
On Wed, 2006-01-04 at 12:34 -0800, Daniel Walker wrote:
> I thought I submitted an identical patch, but maybe I forgot to CC LKML .
Nope, you CC'd LKML:
http://marc.theaimsgroup.com/?l=linux-kernel&m=113630942301200&w=2
Ingo has been really busy with getting the mutex stuff into mainline, so
he hasn't had time to update RT or even work on it very much. Maybe,
I'll start up a patch website to hold patches to Ingo's -rt code until
he has time to work on it again.
-- Steve
On Wed, 2006-01-04 at 17:12 -0500, Steven Rostedt wrote:
> Ingo has been really busy with getting the mutex stuff into mainline, so
> he hasn't had time to update RT or even work on it very much. Maybe,
> I'll start up a patch website to hold patches to Ingo's -rt code until
> he has time to work on it again.
While Ingo is busy working 48 hours a day on the new mutex
info-structure, the -rt patch set has been a little slow at getting
patch releases. So I've started up a little patch fix repository for
the -rt patch set until Ingo has time to get back to this again.
If you have a problem with the -rt patch set, please CC Ingo and myself,
and I'll try to fix the problem and post a patch here.
My updates will be named -sr, so the current release is at
2.6.15-rt1-sr1. Note, this is more like the stable branch, I'm only
updating bug fixes here. Although this is not as strict as the stable
branch, my adding a patch will be based mainly on how critical it is.
This release contains:
- latest rtc fix (Steven Rostedt)
- ipv6 mcast rwlock initialization fix (Daniel Walker)
Download from:
http://home.stny.rr.com/rostedt/patches/
Patch order is:
http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.15.tar.bz2
http://redhat.com/~mingo/realtime-preempt/patch-2.6.15-rt1
http://home.stny.rr.com/rostedt/patches/patch-2.6.15-rt1-sr1
-- Steve
On Fri, 2006-01-06 at 12:05 -0500, Rick Wright wrote:
> Steve,
>
> I noticed that 2.6.15-rc2 was released in Ingo's usual place yesterday
> (1/5/06) which seems to post-date your 2.6.15-rcX-srX branch. Then,
> earlier today you hinted at an impending 2.6.15-rc1-sr2 release.
> Could you explain how your patches are related to Ingo's -rc2 patch as
> they seem to be somewhat interleaved?
My patches are for going between Ingo's releases. I've even released
2.6.15-rt1-sr2, for the simple reason I didn't notice that 2.6.15-rt2
was out :)
So I'll now download 2.6.15-rt2 and see where it's at. So my suggestion
is to always pick the latest -rt kernel, and if it doesn't work, try my
-sr patch for the same release.
>
> Also, I didn't include the other's on this mail or cc LKML as I'm not
> sure if this was appropriate. If you believe others should be
> included, please include them and forgive my exclusion.
I've added both Ingo and the lkml just so others know. As the title
says, the -sr branch is only while Ingo is busy doing other things, but
I'll keep my branches posted anyways.
-- Steve