All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Weiner <hannes@saeurebad.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] kernel: a few readability changes for nice values
Date: Sun, 19 Oct 2008 01:00:21 +0000	[thread overview]
Message-ID: <871vydiel6.fsf@saeurebad.de> (raw)
In-Reply-To: <a91986340810162050n6cdfe617nf9aa90620cc79084@mail.gmail.com>

Hi Mike,

"Mike Steiner" <mike65536@gmail.com> writes:

> From: Mike Steiner <mike65536@gmail.com>

newline -- see #15 in Documentation/SubmittingPatches

> Replaced raw nice values with constants and added macro to wrap
> range check with a descriptive name.

newline -- as above

> Signed-off-by: Mike Steiner <mike65536@gmail.com>
> ---
> FYI, this is my first kernel patch. I ran checkpatch.pl on it and fixed the
> errors, except for 2 concerning spaces around "<" and ">" because it would
> make the code less readable.
> diff -up linux-2.6.27.1/kernel/sched.c new/kernel/sched.c
> --- linux-2.6.27.1/kernel/sched.c	2008-10-15 16:02:53.000000000 -0700
> +++ new/kernel/sched.c	2008-10-16 20:37:27.000000000 -0700
> @@ -24,6 +24,7 @@
>   *  2007-07-01  Group scheduling enhancements by Srivatsa Vaddagiri
>   *  2007-11-29  RT balancing improvements by Steven Rostedt, Gregory Haskins,
>   *              Thomas Gleixner, Mike Kravetz
> + *  2008-10-16  A few readability changes for nice values by Mike Steiner

Changes are logged through git, no longer in the file headers.

> +#define MIN_NICE (-20)
> +#define MAX_NICE  (19)

IMO, these values are traditionally so well known that the numbers
themselve have symbolic values :)

Best thing is probably to address people mostly working with the code
directly; you can use git to see who that would be.  Then add them to
the CC:.

I suspect that smaller cleanups will be overlooked more easily during
the merge window.  If you don't get a response, just resend it after
things have gotten a bit more calm again.

HTH,

	Hannes

  reply	other threads:[~2008-10-19  1:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-17  3:50 [PATCH] kernel: a few readability changes for nice values Mike Steiner
2008-10-19  1:00 ` Johannes Weiner [this message]
2008-10-20 16:42 ` Randy Dunlap
2008-10-20 16:57 ` Matthew Wilcox

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=871vydiel6.fsf@saeurebad.de \
    --to=hannes@saeurebad.de \
    --cc=kernel-janitors@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 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.