mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Dejin Zheng <zhengdejin5@gmail.com>,
	linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Cc: Brian Norris <briannorris@chromium.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Andy Shevchenko <andy.shevchenko@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	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: Tue, 5 May 2020 08:15:39 +0200	[thread overview]
Message-ID: <c5890e43-4b86-eed2-4de9-caa70743255d@web.de> (raw)
In-Reply-To: <20200505005908.GA8464@nuc8i5>

> Brian, Thanks very much for your reminder,

Reminders can hopefully trigger positive effects.


> These comments have always bothered me.

Thanks for such information.


> Now I can put it on my blacklist.

I find it unfortunate that you choose to adjust your communication preferences
in this direction.
Thus I am curious if other contributors will get more chances to integrate
another bit of advice into your software development attention.

Regards,
Markus

  reply	other threads:[~2020-05-05  6:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-04 13:51 [PATCH] " 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
2020-05-05  0:59       ` [PATCH] " Dejin Zheng
2020-05-05  6:15         ` Markus Elfring [this message]
2020-05-05  8:52         ` 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=c5890e43-4b86-eed2-4de9-caa70743255d@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
all inboxes | Powered by JetHome®