From: Greg KH <greg@kroah.com>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: s390 patches for 2.6.5.
Date: Thu, 8 Apr 2004 09:27:58 -0700 [thread overview]
Message-ID: <20040408162758.GB9702@kroah.com> (raw)
In-Reply-To: <20040408142659.GA1793@mschwid3.boeblingen.de.ibm.com>
On Thu, Apr 08, 2004 at 04:26:59PM +0200, Martin Schwidefsky wrote:
> I've included the zfcp patches in this patch set as well after I "fixed"
> the kfree problem. To get the other bug fixes into mainline I side-stepped
> the kfree issue. There are now release functions for the zfcp_unit and
> zfcp_port objects but I removed the module_exit function as well. Without
> the kfree trick we KNOW module unloading to be racy. So far we know of no
> other feasible solution for this problem. Therefore we removed the support
> for unloading of the zfcp module.
Thank you for fixing this. I don't have a problem with this patch
anymore :)
greg k-h
prev parent reply other threads:[~2004-04-08 16:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-08 14:26 s390 patches for 2.6.5 Martin Schwidefsky
2004-04-08 16:27 ` Greg KH [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=20040408162758.GB9702@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=schwidefsky@de.ibm.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