From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Greg KH <gregkh@suse.de>
Cc: 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: Mon, 09 Jan 2006 13:44:18 +1100 [thread overview]
Message-ID: <1136774659.30123.107.camel@localhost.localdomain> (raw)
In-Reply-To: <1136774203.30123.103.camel@localhost.localdomain>
> 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 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...
Ben.
next prev parent reply other threads:[~2006-01-09 2:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-06 6:37 Greg KH
2006-01-06 18:08 ` Greg KH
2006-01-09 2:36 ` Benjamin Herrenschmidt
2006-01-09 2:44 ` Benjamin Herrenschmidt [this message]
2006-01-09 3:30 ` Greg KH
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=1136774659.30123.107.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.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
Powered by JetHome