lkml.org 
[lkml]   [2008]   [Jul]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] Let HP iLO driver depend on PCI
On Fri, 25 Jul 2008 11:41:31 +0200 Heiko Carstens <heiko.carstens@de.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@canb.auug.org.au> wrote:
> >
> > > Hi Andrew,
> > >
> > > On Thu, 24 Jul 2008 21:56:52 -0700 Andrew Morton <akpm@linux-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.


\
 
 \ /
  Last update: 2008-07-25 11:57    [W:0.057 / U:1.060 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site