linux-kernel - Re: [PATCH] Let HP iLO driver depend on PCI

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20080725025411.bf6d8f74.akpm@linux-foundation.org>
Date:	Fri, 25 Jul 2008 02:54:11 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Heiko Carstens <heiko.carstens@...ibm.com>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	David Altobelli <david.altobelli@...com>,
	Greg Kroah-Hartman <gregkh@...e.de>,
	Christian Borntraeger <borntraeger@...ibm.com>,
	Martin Schwidefsky <schwidefsky@...ibm.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Let HP iLO driver depend on PCI

On Fri, 25 Jul 2008 11:41:31 +0200 Heiko Carstens <heiko.carstens@...ibm.com> wrote:

> On Thu, Jul 24, 2008 at 11:15:19PM -0700, Andrew Morton wrote:
> > On Fri, 25 Jul 2008 15:35:02 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> > 
> > > Hi Andrew,
> > > 
> > > On Thu, 24 Jul 2008 21:56:52 -0700 Andrew Morton <akpm@...ux-foundation.org> wrote:
> > > >
> > > > Three weeks and nobody did an allmodconfig build on linux-next for s390
> > > > or m68k (at least).
> > > 
> > > http://kisskb.ellerman.id.au/kisskb/branch/9/
> > > 
> > 
> > Wow, lots of red.
> > 
> > May I revise my comment?  Three weeks and nobody did anything about the
> > failing allmodconfig builds on linux-next and s390 (at least).
> 
> Not true. I sent patches for all (s390) build failures two weeks ago.
> Nobody cared. Patch for this specific build failure is available
> here http://marc.info/?l=linux-next&m=121577361309086&w=2 .

I doubt if the hpilo developers are watching linux-next for patches.

Stephen will have seen it and he might play the
feed-it-over-to-the-culprit game.  But usually I do that.

It's always appreciated if the patch-creator can identify the
appropriate individuals for the Cc: as well.

> > Is anyone actively monitoring that page and doing the requisite culprit-poking?
> 
> Where to send patches to?

Me, lkml, Stephen, maintainer(s).

> And who takes care they get integrated before
> the merge window opens?

Usually me.  Maintainers will sometimes integrate the fix directly but
the success rate via that route is distressingly low.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/