From: Michal Simek <michal.simek@xilinx.com>
To: Borislav Petkov <bp@alien8.de>, Michal Simek <michal.simek@xilinx.com>
Cc: linux-kernel@vger.kernel.org, monstr@monstr.eu,
"Naga Sureshkumar Relli" <naga.sureshkumar.relli@xilinx.com>,
"Sören Brinkmann" <soren.brinkmann@xilinx.com>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
linux-arm-kernel@lists.infradead.org, linux-edac@vger.kernel.org
Subject: [v2,2/6] edac: synopsys: Add platform specific structures for ddrc controller
Date: Fri, 11 Aug 2017 11:43:43 +0200 [thread overview]
Message-ID: <c0fe2afe-75da-a18f-735f-d2c82e4a070b@xilinx.com> (raw)
On 11.8.2017 11:22, Borislav Petkov wrote:
> On Fri, Aug 11, 2017 at 11:16:15AM +0200, Michal Simek wrote:
>> https://lkml.org/lkml/2017/8/7/105
>> ACK by Rob yesterday.
>
> Ok, pls bounce it to me as I don't have it.
ok.
>
> Also, pls refrain from using lkml.org. Simply do:
>
> http://lkml.kernel.org/r/<Message-ID>
Interesting. I have never seen this before.
http://lkml.kernel.org/r/91fd6532076e4c905b5a228d852bba4941c54a28.1502091561.git.michal.simek@xilinx.com
>
>> I am using patman - u-boot tools for sending patch. It read MAINTAINERS
>> file and copy right people.
>> It has option to explicitly CC people. I need to resend this as v3
>> anyway that's why I will add you there.
>
> Yes, if you send cross-maintainer changes, please make sure to CC them on all
> patches because otherwise stuff like that happens and people start wondering
> where is the rest and so on.
ok. Anyway do you see something else what I should fix in v3?
Thanks,
Michal
---
To unsubscribe from this list: send the line "unsubscribe linux-edac" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2017-08-11 9:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 9:43 Michal Simek [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-08-13 11:35 [v2,2/6] edac: synopsys: Add platform specific structures for ddrc controller Borislav Petkov
2017-08-11 9:22 Borislav Petkov
2017-08-11 9:16 Michal Simek
2017-08-11 9:09 Borislav Petkov
2017-08-07 7:39 Michal Simek
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=c0fe2afe-75da-a18f-735f-d2c82e4a070b@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=bp@alien8.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=monstr@monstr.eu \
--cc=naga.sureshkumar.relli@xilinx.com \
--cc=soren.brinkmann@xilinx.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