From: Markus Elfring <Markus.Elfring@web.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
Coccinelle <cocci@systeme.lip6.fr>
Cc: "Thomas Bogendörfer" <tsbogend@alpha.franken.de>,
"Florian Tobias Schandinat" <FlorianSchandinat@gmx.de>,
"Dejin Zheng" <zhengdejin5@gmail.com>,
"Bartlomiej Zolnierkiewicz" <b.zolnierkie@samsung.com>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
"Ralf Bächle" <ralf@linux-mips.org>,
"Andy Shevchenko" <andy.shevchenko@gmail.com>,
"Thomas Gleixner" <tglx@linutronix.de>
Subject: Re: console: Complete exception handling in newport_probe()
Date: Thu, 23 Apr 2020 17:43:04 +0000 [thread overview]
Message-ID: <11026835-83d0-16eb-f0ea-d779d1de0762@web.de> (raw)
In-Reply-To: <20200423173226.GA75304@kroah.com>
> Please note you are responding to someone who many kernel maintainers,
> myself included, have on their blacklist
You configured your communication filters for some reasons in this way.
> as they are totally unhelpful.
The development views can vary also around my software contributions.
It seems to happen often enough that specific suggestions get accepted
from my selection of change possibilities.
> Please feel free to ignore them like the rest of us do.
This is generally also possible.
But I hope still that our discussions can become more constructive again.
Regards,
Markus
next prev parent reply other threads:[~2020-04-23 17:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 15:53 [PATCH v1] console: fix an issue about ioremap leak Dejin Zheng
2020-04-23 11:10 ` Markus Elfring
2020-04-23 14:29 ` Dejin Zheng
2020-04-23 15:23 ` console: Complete exception handling in newport_probe() Markus Elfring
2020-04-23 17:02 ` Dejin Zheng
2020-04-23 17:22 ` Markus Elfring
2020-04-23 17:32 ` Greg Kroah-Hartman
2020-04-23 17:43 ` Markus Elfring [this message]
2020-04-24 7:46 ` 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=11026835-83d0-16eb-f0ea-d779d1de0762@web.de \
--to=markus.elfring@web.de \
--cc=FlorianSchandinat@gmx.de \
--cc=andy.shevchenko@gmail.com \
--cc=b.zolnierkie@samsung.com \
--cc=cocci@systeme.lip6.fr \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=tglx@linutronix.de \
--cc=tsbogend@alpha.franken.de \
--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).