> Persistent as in: get down on your knees and say "please, please, pretty
> please"?
no as in "listen to the code review feedback and fix things and then try
again"
>
> AFAICT, code is being ignored/rejected for the mere reason that it's not
> considered useful; but who's to say what is useful and what's not?
no things are being reject because they're not being *used*.
Subtle but important difference ;)
But yes, you need to do a moderate amount of "selling" when submitting
code. For a driver that's easy usually, "this is a driver for device X"
and "sold" if the code is reasonable.
For major subsystem changes... you need to explain why it's worth the
disruption. If you can't explain that... then what good would it be ?
--
if you want to mail me at work (and no Mr Al Boldi, you really don't want to), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
