Help!

2.6.19 -mm merge plans

 
  

Goto page Previous  1, 2, 3, 4, 5, 6, 7
Post new topic   General Reply to Topic (not reply to a specific post)    Forums Home -> Kernel (archive) RSS
Next:  [PATCH 2.6.18] [TRIVIAL] Simplify tosh_get_info()..  
Author Message
Roman Zippel
External


Since: Aug 19, 2004
Posts: 405



PostPosted: Mon Sep 25, 2006 7:50 pm    Post subject: Re: 2.6.19 -mm merge plans (NTP changes) [Login to view extended thread Info.]
Archived from groups: linux>kernel (more info?)

Hi,

On Mon, 25 Sep 2006, Ray Lee wrote:

> On 9/25/06, john stultz <johnstul.RemoveThis@us.ibm.com> wrote:
> > I was able to run tests for two days each w/ and w/o the patch I had
> > concerns about. And indeed, it seems if the drift file is reset, the
> > initial convergence is much slower (and this is really what worried me).
> > However once it converges it seems to keep sync as well as the current
> > code.
>
> So slower convergence isn't a regression?

Not really, it makes the clock more stable and less suspectible to
network delays.
I think a big part of the problem is that our calibration code could use
some improvements, I've seen some widely different initial drift values
from one reboot to the next, which is the main reason ntp has to do that
much initial work in the first place.

bye, Roman
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo.RemoveThis@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Back to top
Rafael J. Wysocki
External


Since: May 20, 2006
Posts: 1721



PostPosted: Mon Sep 25, 2006 9:00 pm    Post subject: Re: 2.6.19 -mm merge plans [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

On Monday, 25 September 2006 13:53, Ingo Molnar wrote:
>
> * Nick Piggin <nickpiggin.DeleteThis@yahoo.com.au> wrote:
>
> > OTOH, if we were worried about confusing people, we wouldn't be using
> > the acronym 'rc' for our 'Ridiculous Count', and have our rc1 denote
> > the result of 2 weeks of stuffing the tree with new features and
> > intrusive changes, where people might mistake that for the much more
> > common RC-as-in-'Release Candidate'. Smile

Well, "release" need not mean anything really stable. Let's think of it as
certain state of the tree that has been given a label for future reference.

> oh, we could call the first one -rc0 then Smile

Good idea, IMHO. Smile

Greetings,
Rafael


--
You never change things by fighting the existing reality.
R. Buckminster Fuller
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo.DeleteThis@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Back to top
Ian Kent
External


Since: Apr 11, 2005
Posts: 117



PostPosted: Tue Sep 26, 2006 6:20 am    Post subject: Re: Autofs4 breakage (was 2.6.19 -mm merge plans) [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

On Wed, 20 Sep 2006, Trond Myklebust wrote:

> On Wed, 2006-09-20 at 13:54 -0700, Andrew Morton wrote:
>
> > add-newline-to-nfs-dprintk.patch
> > fs-nfs-make-code-static.patch
> >
> > NFS queue -> Trond.
> >
> > The NFS git tree breaks autofs4 submounts. Still.
>
> I still suspect that is due to a misconfigured selinux setup on your
> machine. If autofs4 expects to be able to do mkdir() on your NFS
> partition (something which in itself is wrong), then selinux should be
> configured to allow it to do so.

As we decided I am working on changing this and it's well on the way to
being completed. It's actually somewhat more complex than just not
creating directories on non-autofs file systems.

Once again, sorry for the delay.

Ian

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo.DeleteThis@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Back to top
Pierre Ossman
External


Since: May 20, 2006
Posts: 202



PostPosted: Wed Oct 11, 2006 4:20 pm    Post subject: Re: 2.6.19 -mm merge plans [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Linus Torvalds wrote:
>
> (Of course, once you get really used to git, you use git _anyway_, and
> then you use cherry-pick and other tools to re-write a cleaned-up version
> of the thing that you originally screwed up because you didn't know what
> you were doing. So you _can_ do this too with git, but that doesn't mean
> that git would necessarily be the best way to do it).
>
> That said, maybe we could help the "fixup" phases evenmore using git. For
> example, right now you can do "git cherry-pick" to transfer individual
> patches, but if you want to combine two commits while cherry-picking, it
> immediately gets more involved (still quite doable: use cherry-pick
> multiple times with the "-n" flag, but it's not as obvious any more).
>

Are there any docs (with examples) on how to work like this? I currently
use StGIT for my patch management, but that has some problems when it
comes to publishing my development tree for others.

Rgds
Pierre

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo.TakeThisOut@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Back to top
Display posts from previous:   
Post new topic   General Reply to Topic (not reply to a specific post)    Forums Home -> Kernel (archive) All times are: Eastern Time (US & Canada) (change)
Goto page Previous  1, 2, 3, 4, 5, 6, 7
Page 7 of 7

 
You can post new topics in this forum
You can reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum