All of lore.kernel.org
 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:02:30 +0200	[thread overview]
Message-ID: <533D7806.8070002@monstr.eu> (raw)
In-Reply-To: <a1a9e47a-069c-4285-9899-d5a58cf532c2@CO9EHSMHS003.ehs.local>

Hi Borislav,

On 03/02/2014 03:32 PM, Punnaiah Choudary Kalluri wrote:
> Add support for ARM Pl310 L2 cache controller parity error
> 
> Signed-off-by: Punnaiah Choudary Kalluri <punnaia@xilinx.com>
> ---
>  .../devicetree/bindings/edac/pl310_edac_l2.txt     |   19 ++
>  drivers/edac/Kconfig                               |    7 +
>  drivers/edac/Makefile                              |    1 +
>  drivers/edac/pl310_edac_l2.c                       |  236 ++++++++++++++++++++
>  4 files changed, 263 insertions(+), 0 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/edac/pl310_edac_l2.txt
>  create mode 100644 drivers/edac/pl310_edac_l2.c

Any comment about this driver?

Thanks,
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/98f56fcb/attachment.sig>

WARNING: multiple messages have this Message-ID (diff)
From: Michal Simek <monstr@monstr.eu>
To: Punnaiah Choudary Kalluri <punnaiah.choudary.kalluri@xilinx.com>
Cc: dougthompson@xmission.com, devicetree@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-edac@vger.kernel.org,
	michal.simek@xilinx.com, robh+dt@kernel.org, pawel.moll@arm.com,
	mark.rutland@arm.com, ijc+devicetree@hellion.org.uk,
	galak@codeaurora.org, rob@landley.net, kpc528@gmail.com,
	kalluripunnaiahchoudary@gmail.com, punnaia@xilinx.com,
	Borislav Petkov <bp@suse.de>
Subject: Re: [RFC PATCH] edac: add support for ARM PL310 L2 cache parity
Date: Thu, 03 Apr 2014 17:02:30 +0200	[thread overview]
Message-ID: <533D7806.8070002@monstr.eu> (raw)
In-Reply-To: <a1a9e47a-069c-4285-9899-d5a58cf532c2@CO9EHSMHS003.ehs.local>

[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]

Hi Borislav,

On 03/02/2014 03:32 PM, Punnaiah Choudary Kalluri wrote:
> Add support for ARM Pl310 L2 cache controller parity error
> 
> Signed-off-by: Punnaiah Choudary Kalluri <punnaia@xilinx.com>
> ---
>  .../devicetree/bindings/edac/pl310_edac_l2.txt     |   19 ++
>  drivers/edac/Kconfig                               |    7 +
>  drivers/edac/Makefile                              |    1 +
>  drivers/edac/pl310_edac_l2.c                       |  236 ++++++++++++++++++++
>  4 files changed, 263 insertions(+), 0 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/edac/pl310_edac_l2.txt
>  create mode 100644 drivers/edac/pl310_edac_l2.c

Any comment about this driver?

Thanks,
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



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

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

Thread overview: 30+ 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-03-02 14:32   ` Punnaiah Choudary Kalluri
2014-03-02 14:32   ` Punnaiah Choudary Kalluri
2014-04-03 15:02   ` Michal Simek [this message]
2014-04-03 15:02     ` Michal Simek
2014-04-03 15:24     ` Borislav Petkov
2014-04-03 15:24       ` Borislav Petkov
2014-04-03 15:25       ` Michal Simek
2014-04-03 15:25         ` Michal Simek
2014-04-09 11:32   ` Borislav Petkov
2014-04-09 11:32     ` Borislav Petkov
2014-04-09 13:18     ` Rob Herring
2014-04-09 13:18       ` Rob Herring
2014-04-09 13:18       ` Rob Herring
2014-04-09 15:19       ` Borislav Petkov
2014-04-09 15:19         ` Borislav Petkov
2014-04-09 17:29         ` Punnaiah Choudary
2014-04-09 17:29           ` Punnaiah Choudary
2014-04-09 17:47           ` Borislav Petkov
2014-04-09 17:47             ` Borislav Petkov
2014-04-09 17:47             ` Borislav Petkov
2014-04-10  6:12             ` Michal Simek
2014-04-10  6:12               ` Michal Simek
2014-04-10  9:02               ` Borislav Petkov
2014-04-10  9:02                 ` Borislav Petkov
2014-04-10 10:09                 ` Michal Simek
2014-04-10 10:09                   ` Michal Simek
2014-04-10 10:09                   ` Michal Simek
2014-04-11 13:14                   ` Borislav Petkov
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=533D7806.8070002@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.