From: Marc Zyngier <maz@kernel.org>
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Jason Cooper <jason@lakedaemon.net>,
linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org,
Xuefeng Li <lixuefeng@loongson.cn>
Subject: Re: [PATCH v3 00/14 RESEND] irqchip: Fix potential resource leaks
Date: Wed, 24 Jun 2020 12:52:05 +0100 [thread overview]
Message-ID: <87817a29a1e2b0ca580108ffb86e1d05@kernel.org> (raw)
In-Reply-To: <73b80d45-1300-4dc3-a0d6-2333b79743b2@loongson.cn>
On 2020-06-24 12:48, Tiezhu Yang wrote:
> On 06/24/2020 05:02 PM, Tiezhu Yang wrote:
>> On 06/24/2020 04:30 PM, Marc Zyngier wrote:
>>> On 2020-06-24 08:44, Tiezhu Yang wrote:
>>>> [git send-email failed due to too many commands,
>>>> so only cc the major related email and resend it,
>>>> sorry for that]
>>>
>>> This is becoming majorly annoying. Please fix your git setup
>>> *before* dumping 57 emails for just 14 patches. You have done
>>> the same thing yesterday, and I would hope you learned from your
>>> mistakes.
>>>
>>> Also, do not repost a series more than once per week. You have
>>> already exceeded your quota by quite a margin.
>>
>> I am very sorry for that.
>> I will wait for some days to resend this patch series.
>
> Hi Marc,
>
> Since each patch of this series is independent, in order to avoid
> git send-email failed, I prefer to resend each patch individually
> and cc more related maintainer or supporter to review.
Don't do that. Just fix your GIT setup.
> If you do not mind, I will resend each patch individually next week.
> Sorry for the noisy and inconvenience.
They are perfectly fine as a series. As the person that will ultimately
merge these patches, I don't want to go and fish individual patches,
which is the best way to miss some.
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2020-06-24 11:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 7:44 [PATCH v3 00/14 RESEND] irqchip: Fix potential resource leaks Tiezhu Yang
2020-06-24 7:44 ` [PATCH v3 01/14 RESEND] irqchip/ath79-misc: " Tiezhu Yang
2020-06-24 7:44 ` [PATCH v3 02/14 RESEND] irqchip/csky-apb-intc: " Tiezhu Yang
2020-06-24 7:45 ` [PATCH v3 03/14 RESEND] irqchip/csky-mpintc: " Tiezhu Yang
2020-06-24 7:45 ` [PATCH v3 04/14 RESEND] irqchip/davinci-aintc: " Tiezhu Yang
2020-06-24 7:45 ` [PATCH v3 05/14 RESEND] irqchip/davinci-cp-intc: " Tiezhu Yang
2020-06-24 7:45 ` [PATCH v3 06/14 RESEND] irqchip/digicolor: " Tiezhu Yang
2020-06-24 7:45 ` [PATCH v3 07/14 RESEND] irqchip/dw-apb-ictl: " Tiezhu Yang
2020-06-24 7:45 ` [PATCH v3 08/14 RESEND] irqchip/ls1x: " Tiezhu Yang
2020-06-24 7:45 ` [PATCH v3 09/14 RESEND] irqchip/mscc-ocelot: " Tiezhu Yang
2020-06-24 7:45 ` [PATCH v3 10/14 RESEND] irqchip/nvic: " Tiezhu Yang
2020-06-24 7:45 ` [PATCH v3 11/14 RESEND] irqchip/omap-intc: Fix potential resource leak Tiezhu Yang
2020-06-24 8:30 ` [PATCH v3 00/14 RESEND] irqchip: Fix potential resource leaks Marc Zyngier
2020-06-24 9:02 ` Tiezhu Yang
2020-06-24 11:48 ` Tiezhu Yang
2020-06-24 11:52 ` Marc Zyngier [this message]
2020-06-28 11:25 ` Aleksandar Markovic
2020-06-28 12:06 ` Marc Zyngier
2020-06-28 12:48 ` Aleksandar Markovic
2020-06-28 16:55 ` Marc Zyngier
2020-06-28 17:00 ` Aleksandar Markovic
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=87817a29a1e2b0ca580108ffb86e1d05@kernel.org \
--to=maz@kernel.org \
--cc=jason@lakedaemon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=lixuefeng@loongson.cn \
--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