Check in new SN2 file from Jes' gettimeoffset() patch.
A message that is not in the archive (sent off-list or not yet received): [email protected]
timer.c
Quoted 17 lines · Linux Kernel Mailing List
ChangeSet 1.1063.9.23, 2003/05/14 17:56:37-07:00, [email protected]
Check in new SN2 file from Jes'
gettimeoffset()patch.# This patch includes the following deltas:
# ChangeSet 1.1063.9.22 -> 1.1063.9.23
# (new) -> 1.1timer.c
#timer.c | 85 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 85 insertions(+)diff -Nru
a/timer.cb/timer.ctimer.c new file +0
-0
^^^^^^^
timer.c line 2
Quoted 3 lines
timer.c new file +2
-0@@ -0,0 +1,85 @@ +/* +* linux/arch/ia64/sn/kernel/sn2/timer.c
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Just wondering, did this file really end up where it belongs?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Quoted 5 lines
timer.c
Quoted 5 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line · Geert Uytterhoeven
diff -Nru
a/timer.cb/timer.ctimer.c new file +0
-0
Geert> ^^^^^^^
Quoted 3 lines
timer.c line 2
Quoted 3 lines
timer.c new file +2
-0@@ -0,0 +1,85 @@ +/* +* linux/arch/ia64/sn/kernel/sn2/timer.c
Geert> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Geert> Just wondering, did this file really end up where it belongs?
I think it did, eventually: there was another change to undo the breakage. What happened is that due to some error, the file ended up in the wrong place in the ia64 linux tree at some point. I then deleted the bogus file. Unfortunately, you can't make bk forgive such sins...
--david