From: Jens Axboe <axboe@suse.de>
To: mikem@beardog.cca.cpqcorp.net
Cc: marcelo.tosatti@cyclades.com, linux-kernel@vger.kernel.org,
mike.miller@hp.com, scott.benesh@hp.com
Subject: Re: cciss updates for 2.4.24-pre1, 1 of 2
Date: Wed, 17 Dec 2003 23:49:36 +0100 [thread overview]
Message-ID: <20031217224936.GM2495@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0312161742220.30010@beardog.cca.cpqcorp.net>
On Tue, Dec 16 2003, mikem@beardog.cca.cpqcorp.net wrote:
> Under certain conditions if the cciss driver fails to load the pointer to
> the hba may be null when trying to free the I/O memory. This patch fixes
> that problem and removes a no longer valid comment.
> This is #1 of 2 and should be applied first. Please consider this patch
> for inclusion in the 2.4.24 kernel.
>
> Thanks,
> mikem
> mike.miller@hp.com
> ------------------------------------------------------------------------------
> diff -burN lx2424pre1.orig/drivers/block/cciss.c lx2424pre1/drivers/block/cciss.c
> --- lx2424pre1.orig/drivers/block/cciss.c 2003-11-28 12:26:19.000000000 -0600
> +++ lx2424pre1/drivers/block/cciss.c 2003-12-16 17:25:50.000000000 -0600
> @@ -2612,7 +2612,6 @@
>
> /* get the address index number */
> cfg_base_addr = readl(c->vaddr + SA5_CTCFG_OFFSET);
> - /* I am not prepared to deal with a 64 bit address value */
> cfg_base_addr &= (__u32) 0x0000ffff;
> #ifdef CCISS_DEBUG
> printk("cfg base address = %x\n", cfg_base_addr);
> @@ -2624,7 +2623,7 @@
> #endif /* CCISS_DEBUG */
> if (cfg_base_addr_index == -1) {
> printk(KERN_WARNING "cciss: Cannot find cfg_base_addr_index\n");
> - release_io_mem(hba[i]);
> + release_io_mem(c);
> return -1;
> }
Looks fine to apply.
--
Jens Axboe
prev parent reply other threads:[~2003-12-17 22:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-16 23:50 mikem
2003-12-17 22:49 ` Jens Axboe [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=20031217224936.GM2495@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=mike.miller@hp.com \
--cc=mikem@beardog.cca.cpqcorp.net \
--cc=scott.benesh@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
all inboxes | Powered by JetHome®