Re: Change of policy for future 2.2 driver submissions
Hi,
On Fri, Jan 05, Linus Torvalds wrote:
[...]
> But that's very different from having somebody like RedHat, SuSE or
> Debian make such a kernel part of their standard package. No, I don't
> expect that they'll switch over completely immediately: that would show
> a lack of good judgement. The prudent approach has always been to have
> both a 2.2.19 and a 2.4.0 kernel on there, and ask the user if he wants
> to test the new kernel first.
Right, but now there is a problem: Software RAID. The RAID code of 2.4.0
is not backwards compatible to the one in 2.2.18; if somebody has used
2.4.0 on softraid and discovers some problem, he can not switch back to
some official 2.2 kernel. In order to make it possible to switch between
kernel releases, every vendor now really is forced to integrate the new
RAID0.90 code to their 2.2 kernel. IMHO this code should be integrated to
the next official 2.2 kernel so people can use whatever they want.
> Linus
-o)
Hubert Mantel Goodbye, dots... /\\
_\_v
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Compatibility issue with 2.2.19pre7
Hi,
is this part of 2.2.19pre7 really a good idea? Even in 2.4.0 the size
field is still a short.
-o)
Hubert Mantel Goodbye, dots... /\\
_\_v
diff -u --new-file --recursive --exclude-from /usr/src/exclude
linux.vanilla/include/linux/nfs.h linux.19p7/include/linux/nfs.h
--- linux.vanilla/include/linux/nfs.h Mon Dec 11 22:13:07 2000
+++ linux.19p7/include/linux/nfs.h Wed Jan 3 00:58:38 2001
@@ -94,7 +94,7 @@
*/
#define NFS_MAXFHSIZE 64
struct nfs_fh {
- unsigned short size;
+ unsigned intsize;
unsigned char data[NFS_MAXFHSIZE];
};
Re: [PATCH] devices.txt bugs
Hi,
On Tue, Jan 02, Geert Uytterhoeven wrote:
> This patch fixes two things:
>
> - Correct the minor numbers for the frame buffer devices. We have room for
> 32 frame buffers since about one year, with more room for future expansion
> to 256. (promised to go in by HPA on Fri, 24 Mar 2000 01:47:05 -0800).
>
> - Fix a typo in the minors for the A2232 serial card
>
> --- linux-2.4.0-current/Documentation/devices.txt.origMon Jan 1 23:30:06
>2001
> +++ linux-2.4.0-current/Documentation/devices.txt Tue Jan 2 11:16:42 2001
> @@ -660,6 +660,12 @@
>
> 29 char Universal frame buffer
> 0 = /dev/fb0 First frame buffer
> + 1 = /dev/fb1 Second frame buffer
> + ...
> + 31 = /dev/fb31 32nd frame buffer
> +
> + Backward compatibility aliases {2.6}
> +
>32 = /dev/fb1 Second frame buffer
How is this supposed to work? /dev/fb1 can either be 29,1 or 29,32. But
not both at the same time.
[...]
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
-o)
Hubert Mantel Goodbye, dots... /\\
_\_v
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Re: Distro kernel patches (was Re: Linux 2.2.18pre4)
Hi,
On Wed, Sep 13, David S. Miller wrote:
> It's an especially amusing situation especially since no vendor has
> shipped a distribution without the raid patches applied to their
> kernel for almost 2 years now.
You have a very interesting definition of "no vendor".
> Later,
> David S. Miller
-o)
Hubert Mantel Goodbye, dots... /\\
_\_v
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Re: Alpha compile problem solved by Andrea (pte_alloc)
Hi,
On Mon, Apr 30, Alan Cox wrote:
> > OTOH x86 is racy and there's no workaround available at the moment.
>
> -ac fixes all known problems there
Is there some place from where one can download all the patches in -ac
kernels as separate patches, not just one monster patch (same way Andrea
is doing)?
I assume you are maintaining them as separate patches anyway in order to
be able to feed them to Linus.
> Alan
-o)
Hubert Mantel Goodbye, dots... /\\
_\_v
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
