For Linux, the "your patches will not be accepted" responses comes approximately after you've ignored a dozen or so Linus rants, each of which will generally first come after you've ignored advice and suggestions from dozens of other people and still insisted on submitting broken stuff. Probably, if you manage to get "banned", at least one rant about you will have featured on HN or Reddit.
Rejecting patches happens often, and usually for mundane reasons. Rejecting people is extreme, and something that's only happened a very, very few times. Off the top of my head I can only remember Kay Sievers [1]. Even then he left the door open ("Let distributions merge it as they need to and maybe we can merge it once it has been proven to be stable by whatever distro that was willing to play games with the developers").
It's hard to get Linus to rant at you in the first place. It is many times as hard to get him to refuse to deal with your code. Basically, you have to persistently be submitting code that the kernel team considers total junk and persistently refuse to acknowledge or deal with the suggestions given.
Rejecting patches happens often, and usually for mundane reasons. Rejecting people is extreme, and something that's only happened a very, very few times. Off the top of my head I can only remember Kay Sievers [1]. Even then he left the door open ("Let distributions merge it as they need to and maybe we can merge it once it has been proven to be stable by whatever distro that was willing to play games with the developers").
It's hard to get Linus to rant at you in the first place. It is many times as hard to get him to refuse to deal with your code. Basically, you have to persistently be submitting code that the kernel team considers total junk and persistently refuse to acknowledge or deal with the suggestions given.
[1] http://lkml.iu.edu/hypermail/linux/kernel/1404.0/01331.html