public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Greg KH <gregkh@suse.de>, Linus Torvalds <torvalds@osdl.org>,
	Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
	Paul Mackerras <paulus@samba.org>
Subject: Re: [GIT PATCH] PCI patches for 2.6.15
Date: Sun, 8 Jan 2006 19:30:57 -0800	[thread overview]
Message-ID: <20060109033057.GA2214@kroah.com> (raw)
In-Reply-To: <1136774659.30123.107.camel@localhost.localdomain>

On Mon, Jan 09, 2006 at 01:44:18PM +1100, Benjamin Herrenschmidt wrote:
> 
> > Hi Greg, what patches specifically have problems ? Paul is just back
> > from vacation and we are trying to catch up with merging the tons of
> > pending powerpc stuffs, but we have a couple of requirements with things
> > in this list, notably my small export of pci_cfg_space_size() which
> > should be trivial, but also Linas error recovery stuff... So if one of
> > these is causing problems, we need to know right now as it means we have
> > to rebase.
> 
> BTW. I looked a linux-pci and only saw 2 complaints about the e1000 and
> sym2 driver patches to implement error recovery. I suppose you could
> just drop those 2 and keep the infrastructure in. However, I'm a bit
> annoyed because Linas did post those patches (and several times I think)
> to the relevant lists, and possibly the maintainers (not sure about
> that) and no comment was ever made...

I also got complaints about a number of the pci_register_driver()
changes, and I was reminded that some of the other patches break some
big IBM boxes in bad ways.

> I find it fairly annoying (and that's not the first time that happens)
> that a major piece of work gets posted publically several times, nobody
> bothers to comment, and by the time it gets send for merging upstream,
> suddenly, people wakeup from all over the place NAK'ing it for all sort
> of reasons, mostly claiming it wasn't properly reviewed by the
> appropriate maintainers...

Heh, it's not the first time, and will not be the last :)

I'll be reposting the series to Linus tomorrow.  I'll include your
export patch, and the core pci error handling changes, so you don't need
to worry about your tree.

thanks,

greg k-h

  reply	other threads:[~2006-01-09  3:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-06  6:37 [GIT PATCH] PCI patches for 2.6.15 Greg KH
2006-01-06 18:08 ` Greg KH
2006-01-09  2:36   ` Benjamin Herrenschmidt
2006-01-09  2:44     ` Benjamin Herrenschmidt
2006-01-09  3:30       ` Greg KH [this message]
2006-01-09 12:03 ` Andrew Morton
2006-01-09 19:20   ` Greg KH

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=20060109033057.GA2214@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@osdl.org \
    --cc=benh@kernel.crashing.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=paulus@samba.org \
    --cc=torvalds@osdl.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