On 07/01/2013 11:29 PM, Richard Yao wrote: > On 07/01/2013 09:56 PM, Greg KH wrote:> On Mon, Jul 01, 2013 at > 09:36:21PM -0400, Richard Yao wrote: >>> That is because fixes for other filesystems are either held back by a >>> lack of system kernel updates or held hostage by regressions in newer >>> kernels on certain hardware. >> >> I have never heard this being a reason for keeping code upstream, what >> do you mean by it? > > This is an issue that end users tend to encounter where changes in a > newer kernel break stuff that they need. One example is nouveau kexec > support. Another is that the nouveau in the first two RCs of Linux 3.7 > (if I recall) broke my display completely.
I probably should clarify that this issue keeps some users from obtaining bug fixes in key components (e.g. their filesystem). That is why I prefer the situation where code lives out-of-tree and works on a variety of kernels over the situation where it is bundled with the kernel for in-tree builds.
signature.asc
Description: OpenPGP digital signature
