Lines Matching +full:fixed +full:- +full:up
8 Greg Kroah-Hartman <greg@kroah.com>
27 -----------------
38 -----
41 to worry about the in-kernel interfaces changing. For the majority of
59 -----------------------
64 - Depending on the version of the C compiler you use, different kernel
71 - Depending on what kernel build options you select, a wide range of
74 - different structures can contain different fields
75 - Some functions may not be implemented at all, (i.e. some locks
76 compile away to nothing for non-SMP builds.)
77 - Memory within the kernel can be aligned in different ways,
80 - Linux runs on a wide range of different processor architectures.
102 -------------------------------
105 keep a Linux kernel driver that is not in the main kernel tree up to
114 instances of where this interface is used within the kernel are fixed up
117 As a specific examples of this, the in-kernel USB interfaces have
122 - A change from a synchronous model of data streams to an asynchronous
126 - A change was made in the way data packets were allocated from the
147 security issue is found, it is fixed in a very short amount of time. A
150 happens, all drivers that use the interfaces were also fixed at the
151 same time, ensuring that the security problem was fixed and could not
156 Kernel interfaces are cleaned up over time. If there is no one using a
164 ----------
169 nightmare, and trying to keep up with an ever changing kernel interface
173 talking about drivers released under a GPL-compatible license here, if your
176 it will be fixed up by the person who did the kernel change in the first
183 - The quality of the driver will rise as the maintenance costs (to the
185 - Other developers will add features to your driver.
186 - Other people will find and fix bugs in your driver.
187 - Other people will find tuning opportunities in your driver.
188 - Other people will update the driver for you when external interface
190 - The driver automatically gets shipped in all Linux distributions
200 ------