linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: monstr@monstr.eu (Michal Simek)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] edac: add support for ARM PL310 L2 cache parity
Date: Thu, 03 Apr 2014 17:25:07 +0200	[thread overview]
Message-ID: <533D7D53.80301@monstr.eu> (raw)
In-Reply-To: <20140403152425.GH9616@pd.tnic>

On 04/03/2014 05:24 PM, Borislav Petkov wrote:
> On Thu, Apr 03, 2014 at 05:02:30PM +0200, Michal Simek wrote:
>> Any comment about this driver?
> 
> It is all on the TODO list. I'll take a look after the merge window
> closes.

Ok. Thank you,
Michal


-- 
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 263 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140403/b5c33707/attachment.sig>

  reply	other threads:[~2014-04-03 15:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1393770760-32550-1-git-send-email-punnaia@xilinx.com>
2014-03-02 14:32 ` [RFC PATCH] edac: add support for ARM PL310 L2 cache parity Punnaiah Choudary Kalluri
2014-04-03 15:02   ` Michal Simek
2014-04-03 15:24     ` Borislav Petkov
2014-04-03 15:25       ` Michal Simek [this message]
2014-04-09 11:32   ` Borislav Petkov
2014-04-09 13:18     ` Rob Herring
2014-04-09 15:19       ` Borislav Petkov
2014-04-09 17:29         ` Punnaiah Choudary
2014-04-09 17:47           ` Borislav Petkov
2014-04-10  6:12             ` Michal Simek
2014-04-10  9:02               ` Borislav Petkov
2014-04-10 10:09                 ` Michal Simek
2014-04-11 13:14                   ` Borislav Petkov

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=533D7D53.80301@monstr.eu \
    --to=monstr@monstr.eu \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).