kernel-janitors.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Marc Zyngier <maz@kernel.org>, Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Jason Cooper <jason@lakedaemon.net>,
	linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH v5 00/14] irqchip: Fix potential resource leaks
Date: Mon, 06 Jul 2020 07:43:35 +0000	[thread overview]
Message-ID: <097e0670-6725-0733-0cf2-3d3c897c4dee@web.de> (raw)
In-Reply-To: <ab1cd9280c7892a0230945ef5ff0880c@kernel.org>

>> v5:
>>   - Modify the commit messages and do some code cleanups
>
> Please stop replying to Markus Elfring, and give people who actually
> care a chance to review this code.

You got the usual chances for the desired patch review.


>                                    Elfring will keep asking you to make
> absolutely pointless changes until you are blue in the face

Can the circumstances evolve in ways under which you would admit
the relevance of (my) suggestions for possible software improvements?

Regards,
Markus

      parent reply	other threads:[~2020-07-06  7:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1593998365-25910-1-git-send-email-yangtiezhu@loongson.cn>
     [not found] ` <1593998365-25910-4-git-send-email-yangtiezhu@loongson.cn>
2020-07-06  6:14   ` [PATCH v5 03/14] irqchip/csky-mpintc: Fix potential resource leaks Markus Elfring
     [not found] ` <1593998365-25910-15-git-send-email-yangtiezhu@loongson.cn>
2020-07-06  7:30   ` [PATCH v5 14/14] irqchip/xilinx-intc: Fix potential resource leak Markus Elfring
     [not found] ` <ab1cd9280c7892a0230945ef5ff0880c@kernel.org>
2020-07-06  7:43   ` 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=097e0670-6725-0733-0cf2-3d3c897c4dee@web.de \
    --to=markus.elfring@web.de \
    --cc=jason@lakedaemon.net \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=yangtiezhu@loongson.cn \
    /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).