From: Denis V. <vd...@il...> - 2005-09-29 05:37:03
|
> > Either BUG, or if(), but not both. Please remove one of them. > > Which one? You decide, I have no strong opinion on this. > > I'll keep the BUG. The reason there's both is that I first wanted to > test whether it would work and then forgot to delete the if. Earlier I > put a BUG_ON(!priv) in _disconnect(), without realising that we get > called after we upload the firmware and there's no priv (or much of > anything else, for that matter) there. Done. > > > how it repercutes on the rest of the system. I'll try to time it and > > > see if we can use a timeout there. > > > > Put an acx_s_msleep() with comment where it is needed. > > Right. > > > Sure. Feel free to replicate all or part of release directory. > > It will sync faster if you do it at my local night. > > I am in ~ GMT-3 timezone. This means that when it's 12:00 in London, > > it 15:00 here. (Somehow windows insists that it's GMT+3 :) > > That's the way I've always counted them. For example, I'm in GMT+1 > (though I shouldn't). That means one hour ahead of Greenwhich > (London). On GMT-3 there's nothing AFAIK. Just the Atlantic. East > Eurpe is on GMT+2/3/. my /etc/localtime is -> /usr/app/glibc-2.3/share/zoneinfo/Europe/Kiev. If I set it to /usr/app/glibc-2.3/share/zoneinfo/Etc/GMT-3 I get correct time (simply without one hour daylight saving shift). "date --utc" displays three hours less than local, which is correct. If I set it to /usr/app/glibc-2.3/share/zoneinfo/Etc/GMT+3, my clock is wrong. I can set clock so that it shows correct time, but then "date --utc" will display three hours MORE THAN local, which is NOT CORRECT. Thus either glibc timezone sign is wrong, or I _am_ in GMT-3. What your "date" and "date --utc" say? -- vda |