From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: SF Markus Elfring <elfring@users.sourceforge.net>,
user-mode-linux-devel@lists.sourceforge.net,
Jeff Dike <jdike@addtoit.com>,
Richard Weinberger <richard@nod.at>,
user-mode-linux-user@lists.sourceforge.net,
kernel-janitors@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
David Miller <davem@davemloft.net>,
Linus Torvalds <torvalds@linux-foundation.org>,
Alexander Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH] um: Use common error handling code in port_listen_fd()
Date: Mon, 23 Oct 2017 12:28:21 +0200 [thread overview]
Message-ID: <20171023102821.GA238@x4> (raw)
In-Reply-To: <20171023084800.p26qcpb7iqyqrz4v@mwanda>
On 2017.10.23 at 11:48 +0300, Dan Carpenter wrote:
> This business of moving the error code to the bottom of the function
> just makes the code less readable. I know you never listen to anyone,
> but you should stop doing it.
How long have we to put up with this?
He just keeps sending these crap patches without listening to anybody,
thereby wasting valuable developer time.
Even browsing LKML is no fun anymore, because his endless mindless patch
series drags everything down qualitywise.
David, would it be possible to simply ban him (SF Markus Elfring) from
vger.kernel.org?
--
Markus
next prev parent reply other threads:[~2017-10-23 10:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 17:29 [PATCH] um: Use common error handling code in port_listen_fd() SF Markus Elfring
2017-10-20 18:06 ` Joe Perches
2017-10-20 18:22 ` SF Markus Elfring
2017-10-23 8:48 ` [PATCH] " Dan Carpenter
2017-10-23 9:01 ` SF Markus Elfring
2017-10-23 9:10 ` Dan Carpenter
2017-10-23 9:17 ` SF Markus Elfring
2017-10-23 10:28 ` Markus Trippelsdorf [this message]
2017-10-23 12:04 ` SF Markus Elfring
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171023102821.GA238@x4 \
--to=markus@trippelsdorf.de \
--cc=dan.carpenter@oracle.com \
--cc=davem@davemloft.net \
--cc=elfring@users.sourceforge.net \
--cc=jdike@addtoit.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@nod.at \
--cc=torvalds@linux-foundation.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=user-mode-linux-user@lists.sourceforge.net \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).