From: Gregory Haskins <ghaskins@novell.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: mingo@elte.hu, rostedt@home.goodmis.org, peterz@infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] sched: de CPP-ify the scheduler code
Date: Wed, 14 Jan 2009 10:28:59 -0500 [thread overview]
Message-ID: <496E04BB.5010206@novell.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0901141009410.6759@gandalf.stny.rr.com>
[-- Attachment #1: Type: text/plain, Size: 948 bytes --]
Steven Rostedt wrote:
>
> On Wed, 14 Jan 2009, Gregory Haskins wrote:
>
>
>>
>> -#define enqueue_pushable_task(rq, p) do { } while (0)
>> -#define dequeue_pushable_task(rq, p) do { } while (0)
>> +static inline
>> +void enqueue_pushable_task(struct rq *rq, struct task_struct *p) {}
>> +static inline
>> +void dequeue_pushable_task(struct rq *rq, struct task_struct *p) {}
>>
>
> Wouldn't the above look better as:
>
> static inline void
> enqueue_pushable_task(struct rq *rq, struct task_struct *p)
> {
> }
> static inline void
> dequeue_pushable_task(struct rq *rq, struct task_struct *p)
> {
> }
>
>
I personally like to try to keep disabled functions ideally as close to
one line as possible to visually denote that it isn't doing anything
worth looking at. But I don't feel strongly either way, so whatever
makes you guys happy. :)
Shall I convert the others to this form as well?
-Greg
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2009-01-14 15:26 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 14:24 [git pull] RT scheduler updates for tip Gregory Haskins
2008-12-08 14:32 ` Ingo Molnar
2008-12-08 16:05 ` [PATCH] sched: fix build failure in kernel/sched_rt.c Ingo Molnar
2008-12-08 16:14 ` Gregory Haskins
2008-12-08 16:12 ` [git pull] RT scheduler updates for tip Ingo Molnar
2008-12-08 16:57 ` Gregory Haskins
2008-12-09 14:35 ` Gregory Haskins
2008-12-12 11:34 ` Ingo Molnar
2008-12-12 11:49 ` Ingo Molnar
2008-12-29 15:37 ` Gregory Haskins
2008-12-29 18:13 ` Gregory Haskins
2009-01-11 4:01 ` Ingo Molnar
2009-01-11 9:53 ` Ingo Molnar
2009-01-12 14:45 ` Gregory Haskins
2009-01-12 14:45 ` Ingo Molnar
2009-01-12 15:05 ` Gregory Haskins
2009-01-12 19:23 ` [git pull] fixes for tip/sched/rt Gregory Haskins
2009-01-13 1:43 ` Ingo Molnar
2009-01-13 2:37 ` [PATCH v2] sched: fix build error in kernel/sched_rt.c when RT_GROUP_SCHED && !SMP Gregory Haskins
2009-01-14 8:01 ` Ingo Molnar
2009-01-14 10:54 ` Peter Zijlstra
2009-01-14 11:03 ` Ingo Molnar
2009-01-14 13:21 ` Gregory Haskins
2009-01-14 14:46 ` [PATCH v3 0/2] fixes for tip/sched/rt Gregory Haskins
2009-01-14 14:46 ` [PATCH v3 1/2] sched: de CPP-ify the scheduler code Gregory Haskins
2009-01-14 15:11 ` Steven Rostedt
2009-01-14 15:28 ` Gregory Haskins [this message]
2009-01-14 14:46 ` [PATCH v3 2/2] sched: fix build error in kernel/sched_rt.c when RT_GROUP_SCHED && !SMP Gregory Haskins
2009-01-15 12:30 ` [PATCH v3 0/2] fixes for tip/sched/rt Ingo Molnar
2009-01-16 13:35 ` Ingo Molnar
2009-01-16 13:45 ` Gregory Haskins
2009-01-16 13:46 ` Peter Zijlstra
2009-01-16 14:02 ` Gregory Haskins
2009-01-16 14:02 ` Ingo Molnar
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=496E04BB.5010206@novell.com \
--to=ghaskins@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=rostedt@home.goodmis.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.