From: Andrew Morton <akpm@linux-foundation.org>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
David Altobelli <david.altobelli@hp.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Let HP iLO driver depend on PCI
Date: Fri, 25 Jul 2008 02:54:11 -0700 [thread overview]
Message-ID: <20080725025411.bf6d8f74.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080725094131.GA4436@osiris.boeblingen.de.ibm.com>
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.
next prev parent reply other threads:[~2008-07-25 9:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 2:20 [PATCH] Let HP iLO driver depend on PCI Heiko Carstens
2008-07-25 4:56 ` Andrew Morton
2008-07-25 5:35 ` Stephen Rothwell
2008-07-25 6:15 ` Andrew Morton
2008-07-25 7:13 ` Stephen Rothwell
2008-07-25 9:41 ` Heiko Carstens
2008-07-25 9:54 ` Andrew Morton [this message]
2008-07-25 10:30 ` Heiko Carstens
2008-07-25 13:46 ` Altobelli, David
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=20080725025411.bf6d8f74.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=borntraeger@de.ibm.com \
--cc=david.altobelli@hp.com \
--cc=gregkh@suse.de \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=sfr@canb.auug.org.au \
/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.