public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gregory Haskins <ghaskins@novell.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Peter Zijlstra <peterz@infradead.org>,
	rostedt@home.goodmis.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] sched: fix build error in kernel/sched_rt.c when	RT_GROUP_SCHED && !SMP
Date: Wed, 14 Jan 2009 08:21:40 -0500	[thread overview]
Message-ID: <496DE6E4.1010209@novell.com> (raw)
In-Reply-To: <20090114110356.GK2913@elte.hu>

[-- Attachment #1: Type: text/plain, Size: 1267 bytes --]

Ingo Molnar wrote:
> * Peter Zijlstra <peterz@infradead.org> wrote:
>
>   
>> On Wed, 2009-01-14 at 09:01 +0100, Ingo Molnar wrote:
>>     
>>> * Gregory Haskins <ghaskins@novell.com> wrote:
>>>
>>>       
>>>> +#define dec_rt_group(rt_se, rt_rq) do { } while (0)
>>>>         
>>> Please dont _ever_ introduce new CPP macros into core kernel code, and if 
>>> you see existing once, please fix them to be proper C inline functions. 
>>> (there's a few other new macros in your patchset)
>>>       
>> Generally good advice, and certainly doable in this case. But in some 
>> very rare occasions I've had to use CPP in order to avoid silly header 
>> dependency hell -- I think we should add comments in such cases as to 
>> why we use CPP.
>>     
>
> yeah - that's why i qualified it with 'core kernel code', not 'headers'. 
>
> (But even in the dependency spaghetti case the right solution is to clean 
> up the header dependencies. It's just very hard in most cases due to most 
> folks running on x86 and there being 20+ other architectures they cannot 
> really test. So the dependency hell tends to grow not shrink. )
>
>   

Hey guys,
  Sorry, wasn't aware of that rule.  Ill spin a v3 and send it out later
today.

-Greg


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

  reply	other threads:[~2009-01-14 13:18 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 [this message]
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
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=496DE6E4.1010209@novell.com \
    --to=ghaskins@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox