linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Brian Norris <briannorris@chromium.org>,
	linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
	Andy Shevchenko <andy.shevchenko@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	Dejin Zheng <zhengdejin5@gmail.com>,
	Kalle Valo <kvalo@codeaurora.org>,
	Stanislaw Gruszka <sgruszka@redhat.com>,
	Yan-Hsuan Chuang <yhchuang@realtek.com>
Subject: Re: net: rtw88: fix an issue about leak system resources
Date: Mon, 4 May 2020 19:19:10 +0200	[thread overview]
Message-ID: <db4c6000-ccc3-6113-96db-b7a69297156d@web.de> (raw)
In-Reply-To: <CA+ASDXOJ2CSzdgos4Y8Wd7iZjRUkrMN=Ma0_-ujG8bihGzPKkQ@mail.gmail.com>

> Markus is not really providing any value to the community.

The opinions can vary also around my contributions.


> Just search for his recent mail history -- it's all silly commit message
> nitpicking of little value.

I dare to point questionable implementation (and/or wording) details out.


> He's been blacklisted by a number of people already:

Such communication settings can happen for some reasons.


> Some people continue to humor him, but it's mostly just a waste of
> their time, as this has been going on for years. Just look at searches
> like this, and tell me whether they produce anything useful:
>
> https://lkml.kernel.org/lkml/?q=%22markus+elfring%22&o=5000

How do you think about to take another look at published software development
statistics in constructive ways?

Regards,
Markus

  parent reply	other threads:[~2020-05-04 17:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-04 13:51 [PATCH] net: rtw88: fix an issue about leak system resources Markus Elfring
     [not found] ` <20200504144206.GA5409@nuc8i5>
2020-05-04 15:00   ` Markus Elfring
2020-05-04 17:03     ` Brian Norris
2020-05-04 17:19       ` Markus Elfring
2020-05-04 17:19       ` Markus Elfring [this message]
2020-05-05  0:59       ` [PATCH] " Dejin Zheng
2020-05-05  6:15         ` Markus Elfring
2020-05-05  8:52         ` [PATCH] " Andy Shevchenko
2020-05-05  9:03           ` net: rtw88: Fix an issue about leaking " 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=db4c6000-ccc3-6113-96db-b7a69297156d@web.de \
    --to=markus.elfring@web.de \
    --cc=andy.shevchenko@gmail.com \
    --cc=briannorris@chromium.org \
    --cc=davem@davemloft.net \
    --cc=kvalo@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sgruszka@redhat.com \
    --cc=yhchuang@realtek.com \
    --cc=zhengdejin5@gmail.com \
    /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).