remove drivers/fc4/
A message that is not in the archive (sent off-list or not yet received): [email protected]
From: Christoph Hellwig <[email protected]>
Subject: [PATCH] remove drivers/fc4/
Date: Sun, 19 Jun 2005 13:37:24 +0200
Quoted 6 lines
This code doesn't work since 2.2.x times, uses various obsolete APIs, pokes into the midlayer code where it shouldn't and thus won't even have a chance to compile after my next round of patches.
Let's get rid of it, anyone who wants to resurrect it can find it in the archives, and it'll require a major rewrite anyway.
It does work for some people. People do use it.
It built just fine before changes started going in lately. Removing it is not a magic escape hatch you get to use because you want to change some interfaces but don't know how to do so without breaking the driver.
Quoted 4 lines · David S. Miller
From: Christoph Hellwig <[email protected]>
Subject: [PATCH] removedrivers/fc4/
Date: Sun, 19 Jun 2005 13:37:24 +0200
Quoted 8 lines
Quoted 6 lines
This code doesn't work since 2.2.x times, uses various obsolete APIs, pokes into the midlayer code where it shouldn't and thus won't even have a chance to compile after my next round of patches.
Let's get rid of it, anyone who wants to resurrect it can find it in the archives, and it'll require a major rewrite anyway.
It does work for some people. People do use it.
Who? looking at sparclinux doesn't show anyone who got it working since 2.2.x days.
Quoted 5 lines
It built just fine before changes started going in lately. Removing it is not a magic escape hatch you get to use because you want to change some interfaces but don't know how to do so without breaking the driver.
It's doing completely stupid things about poking into EH internals. This never was an API and no other driver does this - and I'm not going to do anything but if 0'ing large parts of the drivers to 'fix' the build because there's very little that wasn't totally broken before.
Note that you actually agreed on removing them from the tree back in June 2004.
From: Christoph Hellwig <[email protected]>
Date: Sun, 19 Jun 2005 22:40:08 +0200
Quoted 2 lines
Note that you actually agreed on removing them from the tree back in June 2004.
Currently, I'm giving Ben Collins a little bit more time to try and get his setup working.
If you really want to kill the driver, feel free.
Quoted 9 lines · Christoph Hellwig
Quoted 8 lines · David S. Miller
From: Christoph Hellwig <[email protected]>
Subject: [PATCH] removedrivers/fc4/
Date: Sun, 19 Jun 2005 13:37:24 +0200Quoted 4 lines
This code doesn't work since 2.2.x times, uses various obsolete APIs, pokes into the midlayer code where it shouldn't and thus won't even have a chance to compile after my next round of patches.
Quoted 7 lines
Quoted 4 lines
Quoted 2 lines
Let's get rid of it, anyone who wants to resurrect it can find it in the archives, and it'll require a major rewrite anyway.
It does work for some people. People do use it.
Who? looking at sparclinux doesn't show anyone who got it working since 2.2.x days.
Umm... sparc64 does work with 2.6. I don't have any fiberchannel hardware in question, but both 2.4 and 2.6 work on Ultra just fine. Ought to try and resurrect the quad-SS20 box and see what's the situation with sparc32 one of these days...
Quoted 7 lines · Al Viro
Quoted 2 lines
Who? looking at sparclinux doesn't show anyone who got it working since 2.2.x days.
Umm... sparc64 does work with 2.6. I don't have any fiberchannel hardware in question, but both 2.4 and 2.6 work on Ultra just fine. Ought to try and resurrect the quad-SS20 box and see what's the situation with sparc32 one of these days...
Huh? 'sparclinux' in this contect is the sparclinux mainlinglist, and 'it' refers to drivers/fc4