From: "H. Peter Anvin" <hpa@zytor.com>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Arch Mailing List <linux-arch@vger.kernel.org>,
Ralf Baechle <ralf@linux-mips.org>,
Sam Ravnborg <sam@ravnborg.org>, Paul Mundt <lethal@linux-sh.org>,
Richard Henderson <rth@twiddle.net>,
Michael Starvik <starvik@axis.com>,
David Howells <dhowells@redhat.com>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Hirokazu Takata <takata@linux-m32r.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Roman Zippel <zippel@linux-m68k.org>,
"William L. Irwin" <sparclinux@vger.kernel.org>,
Chris Zankel <chris@zankel.net>
Subject: Re: [PATCH] Avoid overflows in kernel/time.c (version 3)
Date: Mon, 17 Dec 2007 15:33:45 -0800 [thread overview]
Message-ID: <47670759.4040208@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0712180028430.32270@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Dec 17 2007 13:53, H. Peter Anvin wrote:
>
>> index 0000000..fd46b3d
>> --- /dev/null
>> +++ b/kernel/timeconst.pl
>
> Could this live in scripts/ too? (And use CodingStyle?)
Why should it live in scripts/ rather than where it is used? scripts/
is used either for global scripts or scripts which are used manually.
Other scripts are not centralized there.
CodingStyle is applicable to C code, not to scripts as far as I can tell.
-hpa
WARNING: multiple messages have this Message-ID (diff)
From: "H. Peter Anvin" <hpa@zytor.com>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Arch Mailing List <linux-arch@vger.kernel.org>,
Ralf Baechle <ralf@linux-mips.org>,
Sam Ravnborg <sam@ravnborg.org>, Paul Mundt <lethal@linux-sh.org>,
Richard Henderson <rth@twiddle.net>,
Michael Starvik <starvik@axis.com>,
David Howells <dhowells@redhat.com>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Hirokazu Takata <takata@linux-m32r.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Roman Zippel <zippel@linux-m68k.org>,
"William L. Irwin" <sparclinux@vger.kernel.org>,
Chris Zankel <chris@zankel.net>
Subject: Re: [PATCH] Avoid overflows in kernel/time.c (version 3)
Date: Mon, 17 Dec 2007 23:33:45 +0000 [thread overview]
Message-ID: <47670759.4040208@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0712180028430.32270@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Dec 17 2007 13:53, H. Peter Anvin wrote:
>
>> index 0000000..fd46b3d
>> --- /dev/null
>> +++ b/kernel/timeconst.pl
>
> Could this live in scripts/ too? (And use CodingStyle?)
Why should it live in scripts/ rather than where it is used? scripts/
is used either for global scripts or scripts which are used manually.
Other scripts are not centralized there.
CodingStyle is applicable to C code, not to scripts as far as I can tell.
-hpa
next prev parent reply other threads:[~2007-12-17 23:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 21:53 [PATCH] Avoid overflows in kernel/time.c (version 3) H. Peter Anvin
2007-12-17 21:53 ` H. Peter Anvin
2007-12-17 23:29 ` Jan Engelhardt
2007-12-17 23:29 ` Jan Engelhardt
2007-12-17 23:33 ` H. Peter Anvin [this message]
2007-12-17 23:33 ` H. Peter Anvin
2007-12-18 12:32 ` Jan Engelhardt
2007-12-18 12:32 ` Jan Engelhardt
-- strict thread matches above, loose matches on Subject: below --
2007-12-17 23:45 [PATCH] Avoid overflows in kernel/time.c (version 4) H. Peter Anvin
2007-12-17 23:45 ` H. Peter Anvin
2007-12-18 5:37 ` Sam Ravnborg
2007-12-18 5:37 ` Sam Ravnborg
2007-12-17 21:53 ` [PATCH] Avoid overflows in kernel/time.c (version 5) H. Peter Anvin
2007-12-17 21:53 ` H. Peter Anvin
2007-12-23 2:58 ` Andrew Morton
2007-12-23 2:58 ` Andrew Morton
2007-12-23 5:52 ` [PATCH] Avoid overflows in kernel/time.c (version 6) H. Peter Anvin
2007-12-23 5:52 ` H. Peter Anvin
2007-12-24 0:14 ` [PATCH] Avoid overflows in kernel/time.c (version 5) Roman Zippel
2007-12-24 0:14 ` Roman Zippel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47670759.4040208@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=chris@zankel.net \
--cc=dhowells@redhat.com \
--cc=geert@linux-m68k.org \
--cc=jengelh@computergmbh.de \
--cc=lethal@linux-sh.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=rth@twiddle.net \
--cc=sam@ravnborg.org \
--cc=sparclinux@vger.kernel.org \
--cc=starvik@axis.com \
--cc=takata@linux-m32r.org \
--cc=ysato@users.sourceforge.jp \
--cc=zippel@linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.