public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexey Dobriyan <adobriyan@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.32-rc4
Date: Mon, 12 Oct 2009 17:29:18 +0400	[thread overview]
Message-ID: <20091012132917.GA4900@x200> (raw)
In-Reply-To: <20091012082950.GA2270@elte.hu>

On Mon, Oct 12, 2009 at 10:29:50AM +0200, Ingo Molnar wrote:
> * Linus Torvalds <torvalds@linux-foundation.org> wrote:
> 
> > Alexey Dobriyan (2):
> >       headers: remove sched.h from interrupt.h
> 
> This commit broke the -rc4 build in numerous ways on x86:
> 
>   drivers/pci/hotplug/cpqphp.h: In function ???wait_for_ctrl_irq???:
>   drivers/pci/hotplug/cpqphp.h:730: error: implicit declaration of function ???signal_pending???
> 
>   drivers/char/rtc.c: In function 'rtc_interrupt':
>   drivers/char/rtc.c:271: error: 'TASK_INTERRUPTIBLE' undeclared (first use in this function)
>   drivers/char/rtc.c:271: error: (Each undeclared identifier is reported only once
> 
> (I'll send fixes for the build failures as followups to this mail.)
> 
> Beyond being buggy there's two workflow problems with the commit.
> 
> Firstly, the commit log concentrates on the m68k situation while in 
> reality more testing on x86 would have been much more important to the 
> end result. If we break m68k with a header cleanup it's far less of a 
> practical problem than if we break thousands of x86 boxes. I find this 
> kind of artificially inflated focus on cross-testing (without properly 
> weighting platforms) harmful.
> 
> Secondly, i'm wondering why the original mail to lkml:
> 
>   Date: Wed, 7 Oct 2009 17:09:06 +0400
>   From: Alexey Dobriyan <adobriyan@gmail.com>
>   To: torvalds@linux-foundation.org
>   Subject: [PATCH] headers: remove sched.h from interrupt.h
>   Cc: linux-kernel@vger.kernel.org
> 
> Wasnt Cc:-ed to the affected maintainers?

To whom? All 42 of them?

> As a result the patch wasnt 
> tested by any maintainer tree before it was sent to Linus. The change is 
> good but obviously needs to be done more carefully, there are a _lot_ of 
> hidden header dependencies in the kernel, especially related to sched.h.
> 
> We are doing regular header cleanup patches in -tip and have the 
> infrastructure to test them properly as well, so this change could have 
> been done via either the scheduler tree and the interrupt tree. We also 
> cross-test to all other architectures.

Me too.

This patch was tested on ~300 configs (allmodconfigs and defconfigs) _and_
randconfigs on i386 and x86_64. I'm sorry I don't have more compile time.

> Alexey, could you please Cc: affected maintainers in the future, so that 
> we can avoid such problems?

Probably.

The problem I have with -tip is that god knows what's in there,
so any header dependency removed might very well be unrelated to mainline.

  parent reply	other threads:[~2009-10-12  9:30 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-11 21:58 Linux 2.6.32-rc4 Linus Torvalds
2009-10-12  7:42 ` [origin tree build failure] [PATCH] Revert "USB: musb: make HAVE_CLK support optional" Ingo Molnar
2009-10-12 13:05   ` Mike Frysinger
2009-10-12 14:29     ` Greg KH
2009-10-12 14:39       ` Mike Frysinger
2009-10-12 15:00         ` Ingo Molnar
2009-10-12 15:09           ` Mike Frysinger
2009-10-12 13:49   ` [PATCH] USB: musb: invert arch depend string Mike Frysinger
2009-10-12 14:28     ` Greg KH
2009-10-12 15:02       ` Ingo Molnar
2009-10-12  8:05 ` [crash] NULL pointer dereference at IP: [<ffffffff812e9ccb>] uart_close+0x2a/0x1e4 Ingo Molnar
2009-10-12  9:19   ` Ingo Molnar
2009-10-12  9:27     ` Ingo Molnar
2009-10-12 11:25       ` Ingo Molnar
2009-10-12 11:45         ` Alan Cox
2009-10-12 11:55           ` Ingo Molnar
2009-10-12 12:22             ` Ingo Molnar
2009-10-12 13:06               ` Alan Cox
2009-10-12 14:23                 ` Ingo Molnar
2009-10-12 16:19   ` Linus Torvalds
2009-10-12 16:26     ` Ingo Molnar
2009-10-12 16:28     ` Ingo Molnar
2009-10-12 16:37     ` Linus Torvalds
2009-10-12 17:13       ` [PATCH] tty, serial: Fix race and NULL check in uart_close() Ingo Molnar
2009-10-12  8:29 ` Linux 2.6.32-rc4 Ingo Molnar
2009-10-12  8:30   ` [origin tree build failure] [PATCH] headers: Fix build in drivers/pci/hotplug/cpqphp.h Ingo Molnar
2009-10-12  8:32   ` [origin tree build failure] [PATCH] headers: Fix build in drivers/char/rtc.c Ingo Molnar
2009-10-12  8:40   ` [origin tree build failure] [PATCH] headers: Fix build in drivers/net/wan/pci200syn.c Ingo Molnar
2009-10-12  9:11   ` [origin tree build failure] [PATCH] headers: Fix build in drivers/net/wan/n2.c Ingo Molnar
2009-10-12  9:16   ` [origin tree build failure] [PATCH] headers: Fix build in drivers/net/wan/c101.c Ingo Molnar
2009-10-12 10:06   ` [origin tree build failure] [PATCH] headers: Fix build in drivers/char/genrtc.c Ingo Molnar
2009-10-12 13:29   ` Alexey Dobriyan [this message]
2009-10-12  9:43     ` Linux 2.6.32-rc4 Ingo Molnar
2009-10-12 13:34   ` Alexey Dobriyan
2009-10-12  9:48     ` Ingo Molnar
2009-10-12 14:22   ` [origin tree build failure] [PATCH] headers: Fix build in drivers/char/sonypi.c Ingo Molnar
2009-10-12 13:01 ` Linux 2.6.32-rc4 Thomas Meyer

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=20091012132917.GA4900@x200 \
    --to=adobriyan@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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