>> Look I got off on the wrong start and I am starting to improve my repo but seems > > If you think you're improving your rep with these poor patches, you're delusional. > >> impossible if people are just going to forget about my good patches. > > We'll discuss that when you actually submit one that isn't a steaming > pile of dingo's kidneys. > > Do yourself a favor - try to resist the temptation to post a patch for at > least 30 to 60 days, *no matter how correct you think it is*. > Plz start listening to what people are telling you. Don't post patches here. If you want to make them, fine. Keep them in your local machine for now. Heed to the advice of seniors here otherwise people will just start ignoring you _completely_ and you won't get any help after that. Also, I've observed that you're not trying to understand what the code is doing. You're looking at every build error/bug as a C programming problem (which too unfortunately you're not understanding completely) and have no clue of the context in which it's written. Thats why Valdis and many others are finding so many faults in your 'patches'. They are wrong at both levels! Please go through some C tutorials and get a good grasp of the language. Only _then_ attempt to get your hands dirty with kernel code. This is my last advice. After this, I will delete all patch related emails from you without reading it. Good luck, -mandeep > _______________________________________________ > Kernelnewbies mailing list > Kernelnewbies@xxxxxxxxxxxxxxxxx > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies > _______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
