From: Christoph Hellwig <hch@ns.caldera.de>
To: juhl@eisenstein.dk (Jesper Juhl)
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] various minor cleanups against 2.4.13-pre3 - comments requested
Date: Tue, 16 Oct 2001 21:59:08 +0200 [thread overview]
Message-ID: <200110161959.f9GJx8T03152@ns.caldera.de> (raw)
In-Reply-To: <3BCC8C88.58BBCC39@eisenstein.dk>
In article <3BCC8C88.58BBCC39@eisenstein.dk> you wrote:
> kernel/exec_domain.c :
> Contrary to most other files in the kernel source the functions
> in exec_domain.c are defined with the
> return values on a line by themselves. Most places in kernel
> source have the entire function definition
> on a single line (as long as it does not exceed 80 chars in
> length). So I moved the function definitions
> onto a single line.
NO. This file is maintained and that style is intentional.
(BTW, you could compare it to output of scripts/Lindent..)
> kernel/exec_domain.c : get_exec_domain_list()
> The len variable (signed) is compared to PAGE_SIZE (unsigned).
> Changing len to "unsigned int" avoids
> comparison between signed and unsigned.
Looks sane to me.
Christoph
--
Of course it doesn't work. We've performed a software upgrade.
next prev parent reply other threads:[~2001-10-16 19:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-16 19:37 Jesper Juhl
2001-10-16 19:52 ` Dave Jones
2001-10-16 20:24 ` [PATCH] various minor cleanups against 2.4.13-pre3 - commentsrequested Jesper Juhl
2001-10-16 19:59 ` Christoph Hellwig [this message]
2001-10-16 20:28 ` [PATCH] various minor cleanups against 2.4.13-pre3 - comments requested Jesper Juhl
2001-10-16 21:34 ` Robert Love
2001-10-17 9:13 ` Martin Dalecki
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=200110161959.f9GJx8T03152@ns.caldera.de \
--to=hch@ns.caldera.de \
--cc=juhl@eisenstein.dk \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®