Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1640275
| From | Joe Perches <joe@perches.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: vmbus: Delete an error message for a failed memory allocation in vmbus_device_create() |
| Date | 2017-05-12 10:00 +0200 |
| Message-ID | <tGdEu-1eG-15@gated-at.bofh.it> (permalink) |
| References | <tFYYN-ax-9@gated-at.bofh.it> <tFYYN-ax-7@gated-at.bofh.it> <tFZia-ha-31@gated-at.bofh.it> <tGd1L-Y4-1@gated-at.bofh.it> <tGdl7-16h-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Fri, 2017-05-12 at 09:32 +0200, SF Markus Elfring wrote: > Will patches be picked up also from contributors who got a special > development reputation anyhow? Yes. Developer reputation matters for somewhat controversial patches being applied as well as non-controversial and obviously correct patches being ignored. Your reputation means most all of your patches fall into the latter category. Look up "wheat and chaff". Your patches are mostly chaff. You have produced many trivial patches that have caused new defects. That is simply unacceptable. Especially when you don't immediately fix the problems you cause. If you would stop producing the trivial and instead channel your efforts into actual bug fixing and logic corrections and not just style modifications with no code impact, your patch acceptance rate would increase. Yes, your daily patch production rate would fall. Likely every reader of LKML but you would be happy. I have given you many suggestions for actual structural improvements to kernel code. You have ignored _all_ of them and I am unlikely to try to interact with you any longer until your wheat:chaff ratio changes.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH 2/4] vmbus: Delete an error message for a failed memory allocation in vmbus_device_create() SF Markus Elfring <elfring@users.sourceforge.net> - 2017-05-11 18:20 +0200
Re: vmbus: Delete an error message for a failed memory allocation in vmbus_device_create() SF Markus Elfring <elfring@users.sourceforge.net> - 2017-05-11 18:40 +0200
Re: vmbus: Delete an error message for a failed memory allocation in vmbus_device_create() Stephen Hemminger <stephen@networkplumber.org> - 2017-05-11 18:50 +0200
Re: [PATCH 2/4] vmbus: Delete an error message for a failed memory allocation in vmbus_device_create() Stephen Hemminger <stephen@networkplumber.org> - 2017-05-11 18:40 +0200
Re: [PATCH 2/4] vmbus: Delete an error message for a failed memory allocation in vmbus_device_create() Dan Carpenter <dan.carpenter@oracle.com> - 2017-05-12 09:20 +0200
Re: vmbus: Delete an error message for a failed memory allocation in vmbus_device_create() SF Markus Elfring <elfring@users.sourceforge.net> - 2017-05-12 09:40 +0200
Re: vmbus: Delete an error message for a failed memory allocation in vmbus_device_create() Joe Perches <joe@perches.com> - 2017-05-12 10:00 +0200
Re: Clarification for general change acceptance SF Markus Elfring <elfring@users.sourceforge.net> - 2017-05-12 10:30 +0200
Re: Clarification for general change acceptance Julia Lawall <julia.lawall@lip6.fr> - 2017-05-12 10:40 +0200
Re: Clarification for general change acceptance SF Markus Elfring <elfring@users.sourceforge.net> - 2017-05-12 10:50 +0200
csiph-web