From: Andrew Morton <akpm@linux-foundation.org>
To: tim.gardner@canonical.com
Cc: tcanonical@tpi.com, bryan.stillwell@hp.com, Mike.Miller@hp.com,
iss_storagedev@hp.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cciss: firmware version is invalid
Date: Mon, 10 Nov 2008 16:55:58 -0800 [thread overview]
Message-ID: <20081110165558.428566ab.akpm@linux-foundation.org> (raw)
In-Reply-To: <49144CB8.8070604@tpi.com>
On Fri, 07 Nov 2008 07:12:08 -0700
Tim Gardner <tcanonical@tpi.com> wrote:
> Stillwell, Bryan wrote:
> > Tim,
> >
> > Thanks for getting this merged, but I believe this patch is preferred
> > over the original one I attached:
> >
> > http://userweb.kernel.org/~akpm/mmotm/broken-out/cciss-fix-regression-firmware-not-displayed-in-procfs-again-and-again.patch
> >
> > The reason for this according to Mike Miller is: "The first fix could be
> > called anytime something changed on the controller such as number of
> > logical volumes, etc. This patch will get called only once for each
> > controller."
> >
> > Thanks,
> > Bryan
>
> applied
>
I'm all confused here.
cciss-fix-regression-firmware-not-displayed-in-procfs-again-and-again.patch
is now in mainline. Are you saying that "cciss: Firmware Version is
invalid" is preferred? That "cciss: Firmware Version is invalid"
should still be applied?
If so, "cciss: Firmware Version is invalid" will need a better title
and changelog, please. The one you have there is pretty skimpy.
reading between the lines, I'm guessing that the driver emits "Firmware
Version is invalid" messages and that this patch somehow fixes that?
next prev parent reply other threads:[~2008-11-11 0:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 20:12 [PATCH] cciss: firmware version is invalid Tim Gardner
2008-11-06 21:11 ` Stillwell, Bryan
2008-11-07 14:12 ` Tim Gardner
2008-11-11 0:55 ` Andrew Morton [this message]
2008-11-11 1:29 ` Tim Gardner
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=20081110165558.428566ab.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Mike.Miller@hp.com \
--cc=bryan.stillwell@hp.com \
--cc=iss_storagedev@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tcanonical@tpi.com \
--cc=tim.gardner@canonical.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