~hc/RK356X_SDK_RELEASE.git

..	..	@@ -169,14 +169,13 @@
169	169	nightmare, and trying to keep up with an ever changing kernel interface
170	170	is also a rough job.
171	171
172		-Simple, get your kernel driver into the main kernel tree (remember we
173		-are talking about GPL released drivers here, if your code doesn't fall
174		-under this category, good luck, you are on your own here, you leech
175		-<insert link to leech comment from Andrew and Linus here>.) If your
176		-driver is in the tree, and a kernel interface changes, it will be fixed
177		-up by the person who did the kernel change in the first place. This
178		-ensures that your driver is always buildable, and works over time, with
179		-very little effort on your part.
	172	+Simple, get your kernel driver into the main kernel tree (remember we are
	173	+talking about drivers released under a GPL-compatible license here, if your
	174	+code doesn't fall under this category, good luck, you are on your own here,
	175	+you leech). If your driver is in the tree, and a kernel interface changes,
	176	+it will be fixed up by the person who did the kernel change in the first
	177	+place. This ensures that your driver is always buildable, and works over
	178	+time, with very little effort on your part.
180	179
181	180	The very good side effects of having your driver in the main kernel tree
182	181	are: