From: Andrew Morton <akpm@linux-foundation.org>
To: Mike Miller <mike.miller@hp.com>
Cc: jens.axboe@oracle.com, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org, fujita.tomonori@lab.ntt.co.jp,
adobriyan@gmail.com
Subject: Re: [PATCH 2/2] cciss:fix regression firmware not displayed in procfs (again and again)
Date: Tue, 21 Oct 2008 15:44:08 -0700 [thread overview]
Message-ID: <20081021154408.ed96c9b3.akpm@linux-foundation.org> (raw)
In-Reply-To: <20081021212322.GA6421@roadking.ldev.net>
On Tue, 21 Oct 2008 16:23:22 -0500
Mike Miller <mike.miller@hp.com> wrote:
> Patch 2 of 2
What happened with "1 of 2"?
> Sorry for the delay. I've been out of the office and the network has been
> down since before lunch CDT. This regression was introduced by commit
> 6ae5ce8e8d4de666f31286808d2285aa6a50fa40.
> This patch fixes a regression where the controller firmware version is not
> displayed in procfs. The previous patch would be called anytime something
> changed. This will get called only once for each controller.
>
> In this patch I again initialize *inq_buff to NULL per Tomo's comments. I
> also use a goto clean 4 instead of returning -ENOMEM if the kzalloc fails.
>
> I hope this finally meets everyones expectations.
>
> Please consider this for inclusion.
>
> Signed-off-by: Mike Miller <mike.miller@hp.com>
So this fix is needed in 2.6.27.x, yes?
next prev parent reply other threads:[~2008-10-21 22:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 21:23 [PATCH 2/2] cciss:fix regression firmware not displayed in procfs (again and again) Mike Miller
2008-10-21 22:44 ` Andrew Morton [this message]
2008-10-22 15:38 ` Miller, Mike (OS Dev)
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=20081021154408.ed96c9b3.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=adobriyan@gmail.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mike.miller@hp.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