No, that's not the name inside the tarball. See my note to Ulrich (or download the file yourself if you don't believe me). As I also said to Ulrich, even if that were the name of the file, I have no way of knowing which lines actually comprise _just_ the "multicast notifier patch." So I have no way of only adding that on top of 2.6.8-rc1.
I need to be able to insmod and rmmod any module, since I'm building distributions. Having to reboot to get rid of a module is not acceptable to me. I'll look over the details of your reply, but I'm not sure that I will be able to do what I want, even with this level of information. If the diffs for 2.6.7 are really that small, putting them up on developerWorks should be no big deal, right? :) And then 2.6.8 should be even easier. ;) Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Arnd Bergmann Sent: Friday, July 16, 2004 8:36 AM To: [EMAIL PROTECTED] Subject: Re: Linux 2.6.7 Patch Status (LONG) On Freitag, 16. Juli 2004 00:32, Post, Mark K wrote: > 1. You're using names for patches that aren't publicly known, such as > "The multicast notifier patch - linux-2.6.5-s390-04-26-april2004.diff" Huh? That's the file name inside the patch tarball on developerWorks. Where else did you get your patches if not there? > 2. You talk of partial reversions, but I have no way of knowing what > parts of what patch were reverted, and which were kept. In case of the zfcp patch, the history is documented in any lkml archive. The developerWorks version of that driver contains a hack to allow module unloading that was not accepted into 2.6.6. The driver works perfectly fine without that patch, you just can't unload the module, but you should not have any reason to do that anyway. -snip- ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
