From: Markus Elfring <Markus.Elfring@web.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Wang Hai <wanghai38@huawei.com>,
Andrew Donnellan <ajd@linux.ibm.com>,
Arnd Bergmann <arnd@arndb.de>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Ian Munsie <imunsie@au1.ibm.com>,
Frederic Barrat <fbarrat@linux.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] cxl: Fix kobject memory leak in cxl_sysfs_afu_new_cr()
Date: Wed, 3 Jun 2020 08:48:40 +0200 [thread overview]
Message-ID: <75959fca-bb32-53b3-e5ee-ab29dfec34d9@web.de> (raw)
In-Reply-To: <20200603061443.GB531505@kroah.com>
> Please note that you are responding to someone that a lot of kernel
> developers and maintainers have blacklisted as being very annoying
I can understand that you can occasionally become annoyed.
> and not helpful at all.
I got the impression that some contributors (including you)
found also a selection of my contributions useful.
> Please do not feel that you need to respond to, or change any patch in
> response to their emails at all.
I suggest to reconsider your responses to provided information once more.
> I strongly recommend you just add them to your filters to not have to
> see their messages. That's what I have done.
I find such an “advice” questionable while it is generally possible
to adjust the communication settings as needed.
Regards,
Markus
prev parent reply other threads:[~2020-06-03 6:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 17:20 [PATCH] cxl: Fix kobject memory leak in cxl_sysfs_afu_new_cr() Markus Elfring
2020-06-03 1:42 ` wanghai (M)
2020-06-03 3:02 ` Michael Ellerman
2020-06-03 5:07 ` Markus Elfring
2020-06-03 6:14 ` [PATCH] " Greg Kroah-Hartman
2020-06-03 6:34 ` wanghai (M)
2020-06-03 6:50 ` Greg Kroah-Hartman
2020-06-03 6:54 ` wanghai (M)
2020-06-03 6:56 ` Markus Elfring
2020-06-03 6:48 ` Markus Elfring [this message]
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=75959fca-bb32-53b3-e5ee-ab29dfec34d9@web.de \
--to=markus.elfring@web.de \
--cc=ajd@linux.ibm.com \
--cc=arnd@arndb.de \
--cc=fbarrat@linux.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=imunsie@au1.ibm.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=wanghai38@huawei.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).