From: Matthew Wilcox <matthew@wil.cx>
To: Adrian Bunk <bunk@stusta.de>
Cc: greg@kroah.com, linux-pci@atrey.karlin.mff.cuni.cz,
linux-kernel@vger.kernel.org, scottm@somanetworks.com,
pcihpd-discuss@lists.sourceforge.net
Subject: Re: [2.6 patch] drivers/pci/hotplug/cpqphp_ctrl.c: board_replaced(): remove dead code
Date: Mon, 27 Feb 2006 09:08:27 -0700 [thread overview]
Message-ID: <20060227160827.GE27759@parisc-linux.org> (raw)
In-Reply-To: <20060227151252.GV3674@stusta.de>
On Mon, Feb 27, 2006 at 04:12:52PM +0100, Adrian Bunk wrote:
> > Why not cc the
> > maintainer for his opinion?
>
> I did, at least I thought I did...
My mistake; I misread cpq as compact. Sorry.
prev parent reply other threads:[~2006-02-27 16:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-26 21:16 [2.6 patch] drivers/pci/hotplug/cpqphp_ctrl.c: board_replaced(): remove dead code Adrian Bunk
2006-02-26 23:55 ` Matthew Wilcox
2006-02-27 15:12 ` Adrian Bunk
2006-02-27 16:08 ` Matthew Wilcox [this message]
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=20060227160827.GE27759@parisc-linux.org \
--to=matthew@wil.cx \
--cc=bunk@stusta.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=pcihpd-discuss@lists.sourceforge.net \
--cc=scottm@somanetworks.com \
/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