Not unusual situation :-/
> As I can understand, the patch is rejected.
Of course :-)
> But what is the reason?
> Is the patch not needed? Or it contains significant bugs?
> Or more functionality is required? Or it simply was not recieved?
Where are you sent patch ? It's just dumb to send patch staight to Linus if
it's not just fix for well-known problem or patch itself is not well-known
and discussed enough in one of few linux kernel related mailing lists...
> Please do not ignore this message. This is the very practical question for
> me.
> Am I allowed to continue the improving of the patch?
Who can stop you ?
> What are the rules for such situations? (This is my first patch and I am
> disoriented).
Patch will not be included in standard kernel till it's not obvious that
functionality provided in patch or problem solved with patch is general
enough.
P.S. Oh, and BTW now there are DEEP rework of some systems in kernel so most
patches are rejected by Linus without any reasons whatsoever. Try to send it
later...
P.P.S. And since interceptors will alffect COMMON path for general subsystems
I expect STRONG feeling against such patch from Linus. Try to discuss problems
and how you interceptors can solve them here rather then try to push patch of
itself. Even if you patch will be rejected for some reason ideas from it can
be borrowed and reimplemented by someone...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/