From: Borislav Petkov <bp@alien8.de>
To: Manish Narani <MNARANI@xilinx.com>
Cc: "robh+dt@kernel.org" <robh+dt@kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"will.deacon@arm.com" <will.deacon@arm.com>,
Michal Simek <michals@xilinx.com>,
"mchehab@kernel.org" <mchehab@kernel.org>,
"mdf@kernel.org" <mdf@kernel.org>,
Edgar Iglesias <edgari@xilinx.com>,
Shubhrajyoti Datta <shubhraj@xilinx.com>,
Naga Sureshkumar Relli <nagasure@xilinx.com>,
Bharat Kumar Gogada <bharatku@xilinx.com>,
"stefan.krsmanovic@aggios.com" <stefan.krsmanovic@aggios.com>,
Srinivas Goud <sgoud@xilinx.com>,
Anirudha Sarangi <anirudh@xilinx.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>
Subject: Re: [PATCH v4 1/4] edac: synps: Add platform specific structures for ddrc controller
Date: Sat, 18 Aug 2018 14:45:37 +0200 [thread overview]
Message-ID: <20180818124537.GA24733@nazgul.tnic> (raw)
In-Reply-To: <DM6PR02MB5227CBDE0742DB55F26F014CC13C0@DM6PR02MB5227.namprd02.prod.outlook.com>
On Sat, Aug 18, 2018 at 10:11:54AM +0000, Manish Narani wrote:
> Ping.
First of all, one ping is enough. If your patchset contained, say, 30
patches, were you really going to send a ping for each one of them?!?!?!
Secondly, you do know that we have merge window right now, don't you?
And during the merge window, people are busy with merge window testing
and sending stuff which is ready, upstream - not reviewing new code
which has absolutely no chance of going in now?
Jeez.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
next prev parent reply other threads:[~2018-08-18 12:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-04 9:25 [PATCH v4 0/4] EDAC: Enhancements to Synopsys EDAC driver Manish Narani
2018-08-04 9:25 ` [PATCH v4 1/4] edac: synps: Add platform specific structures for ddrc controller Manish Narani
2018-08-18 10:11 ` Manish Narani
2018-08-18 12:45 ` Borislav Petkov [this message]
2018-08-21 13:06 ` Borislav Petkov
2018-08-22 12:20 ` Manish Narani
2018-08-04 9:25 ` [PATCH v4 2/4] dt: bindings: Document ZynqMP DDRC in Synopsys documentation Manish Narani
2018-08-07 14:56 ` Rob Herring
2018-08-04 9:25 ` [PATCH v4 3/4] edac: synopsys: Add EDAC ECC support for ZynqMP DDRC Manish Narani
2018-08-21 13:09 ` Borislav Petkov
2018-08-22 13:02 ` Manish Narani
2018-08-22 13:34 ` Borislav Petkov
2018-08-04 9:25 ` [PATCH v4 4/4] arm64: zynqmp: Add DDRC node Manish Narani
2018-08-18 10:12 ` Manish Narani
2018-08-04 16:32 ` [PATCH v4 0/4] EDAC: Enhancements to Synopsys EDAC driver Borislav Petkov
2018-08-06 13:58 ` Manish Narani
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=20180818124537.GA24733@nazgul.tnic \
--to=bp@alien8.de \
--cc=MNARANI@xilinx.com \
--cc=anirudh@xilinx.com \
--cc=bharatku@xilinx.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=edgari@xilinx.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=mdf@kernel.org \
--cc=michals@xilinx.com \
--cc=nagasure@xilinx.com \
--cc=robh+dt@kernel.org \
--cc=sgoud@xilinx.com \
--cc=shubhraj@xilinx.com \
--cc=stefan.krsmanovic@aggios.com \
--cc=will.deacon@arm.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