From: Avi Fishman <avifishman70@gmail.com>
To: Boris Petkov <bp@alien8.de>
Cc: Medad CChien <medadyoung@gmail.com>,
rric@kernel.org, James Morse <james.morse@arm.com>,
YSCHU@nuvoton.com, Mauro Carvalho Chehab <mchehab@kernel.org>,
tony.luck@intel.com, Benjamin Fair <benjaminfair@google.com>,
Patrick Venture <venture@google.com>,
KWLIU@nuvoton.com, Rob Herring <robh+dt@kernel.org>,
JJLIU0@nuvoton.com, KFTING@nuvoton.com,
Nancy Yuen <yuenn@google.com>, Tali Perry <tali.perry1@gmail.com>,
Tomer Maimon <tmaimon77@gmail.com>,
ctcchien@nuvoton.com, linux-edac <linux-edac@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
devicetree <devicetree@vger.kernel.org>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: [PATCH v5 3/3] EDAC: nuvoton: Add NPCM memory controller driver
Date: Mon, 21 Mar 2022 20:28:51 +0200 [thread overview]
Message-ID: <CAKKbWA66rdm11fM2eWpQpSW2aCfFn-9OwJNNN4J2Q4rE2H4vEw@mail.gmail.com> (raw)
In-Reply-To: <37361667-C932-4139-B649-52DE029BDEE5@alien8.de>
On Thu, Mar 17, 2022 at 2:50 PM Boris Petkov <bp@alien8.de> wrote:
>
> On March 17, 2022 1:58:54 AM UTC, Medad CChien <medadyoung@gmail.com> wrote:
> >Add support for Nuvoton NPCM SoC.
> >
> >Signed-off-by: Medad CChien <ctcchien@nuvoton.com>
> >Reported-by: kernel test robot <lkp@intel.com>
>
> What exactly has the robot reported here?
>
> >---
> > drivers/edac/Kconfig | 9 +
> > drivers/edac/Makefile | 1 +
> > drivers/edac/npcm_edac.c | 710 +++++++++++++++++++++++++++++++++++++++
> > 3 files changed, 720 insertions(+)
> > create mode 100644 drivers/edac/npcm_edac.c
>
> I don't see a MAINTAINERS file entry so that people can Cc you on bugs. See the other EDAC drivers for an example.
>
see in MAINTAINERS:
ARM/NUVOTON NPCM ARCHITECTURE
M: Avi Fishman <avifishman70@gmail.com>
M: Tomer Maimon <tmaimon77@gmail.com>
...
F: drivers/*/*npcm*
F: drivers/*/*/*npcm*
Isn't it OK?
> --
> Sent from a small device: formatting sux and brevity is inevitable.
--
Regards,
Avi
WARNING: multiple messages have this Message-ID (diff)
From: Avi Fishman <avifishman70@gmail.com>
To: Boris Petkov <bp@alien8.de>
Cc: KWLIU@nuvoton.com, YSCHU@nuvoton.com, rric@kernel.org,
Benjamin Fair <benjaminfair@google.com>,
linux-edac <linux-edac@vger.kernel.org>,
Patrick Venture <venture@google.com>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>,
JJLIU0@nuvoton.com, ctcchien@nuvoton.com,
Rob Herring <robh+dt@kernel.org>,
Tali Perry <tali.perry1@gmail.com>,
KFTING@nuvoton.com, devicetree <devicetree@vger.kernel.org>,
tony.luck@intel.com, James Morse <james.morse@arm.com>,
Medad CChien <medadyoung@gmail.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Tomer Maimon <tmaimon77@gmail.com>
Subject: Re: [PATCH v5 3/3] EDAC: nuvoton: Add NPCM memory controller driver
Date: Mon, 21 Mar 2022 20:28:51 +0200 [thread overview]
Message-ID: <CAKKbWA66rdm11fM2eWpQpSW2aCfFn-9OwJNNN4J2Q4rE2H4vEw@mail.gmail.com> (raw)
In-Reply-To: <37361667-C932-4139-B649-52DE029BDEE5@alien8.de>
On Thu, Mar 17, 2022 at 2:50 PM Boris Petkov <bp@alien8.de> wrote:
>
> On March 17, 2022 1:58:54 AM UTC, Medad CChien <medadyoung@gmail.com> wrote:
> >Add support for Nuvoton NPCM SoC.
> >
> >Signed-off-by: Medad CChien <ctcchien@nuvoton.com>
> >Reported-by: kernel test robot <lkp@intel.com>
>
> What exactly has the robot reported here?
>
> >---
> > drivers/edac/Kconfig | 9 +
> > drivers/edac/Makefile | 1 +
> > drivers/edac/npcm_edac.c | 710 +++++++++++++++++++++++++++++++++++++++
> > 3 files changed, 720 insertions(+)
> > create mode 100644 drivers/edac/npcm_edac.c
>
> I don't see a MAINTAINERS file entry so that people can Cc you on bugs. See the other EDAC drivers for an example.
>
see in MAINTAINERS:
ARM/NUVOTON NPCM ARCHITECTURE
M: Avi Fishman <avifishman70@gmail.com>
M: Tomer Maimon <tmaimon77@gmail.com>
...
F: drivers/*/*npcm*
F: drivers/*/*/*npcm*
Isn't it OK?
> --
> Sent from a small device: formatting sux and brevity is inevitable.
--
Regards,
Avi
next prev parent reply other threads:[~2022-03-21 18:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 1:58 [PATCH v5 0/3] EDAC: nuvoton: Add nuvoton NPCM memory controller driver Medad CChien
2022-03-17 1:58 ` Medad CChien
2022-03-17 1:58 ` [PATCH v5 1/3] ARM: dts: nuvoton: Add memory controller node Medad CChien
2022-03-17 1:58 ` Medad CChien
2022-03-17 1:58 ` [PATCH v5 2/3] dt-bindings: edac: nuvoton: add NPCM memory controller Medad CChien
2022-03-17 1:58 ` Medad CChien
2022-03-17 1:58 ` [PATCH v5 3/3] EDAC: nuvoton: Add NPCM memory controller driver Medad CChien
2022-03-17 1:58 ` Medad CChien
2022-03-17 8:13 ` kernel test robot
2022-03-17 8:13 ` kernel test robot
2022-03-17 12:50 ` Boris Petkov
2022-03-17 12:50 ` Boris Petkov
2022-03-21 18:28 ` Avi Fishman [this message]
2022-03-21 18:28 ` Avi Fishman
2022-03-21 19:03 ` Borislav Petkov
2022-03-21 19:03 ` 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=CAKKbWA66rdm11fM2eWpQpSW2aCfFn-9OwJNNN4J2Q4rE2H4vEw@mail.gmail.com \
--to=avifishman70@gmail.com \
--cc=JJLIU0@nuvoton.com \
--cc=KFTING@nuvoton.com \
--cc=KWLIU@nuvoton.com \
--cc=YSCHU@nuvoton.com \
--cc=benjaminfair@google.com \
--cc=bp@alien8.de \
--cc=ctcchien@nuvoton.com \
--cc=devicetree@vger.kernel.org \
--cc=james.morse@arm.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=medadyoung@gmail.com \
--cc=openbmc@lists.ozlabs.org \
--cc=robh+dt@kernel.org \
--cc=rric@kernel.org \
--cc=tali.perry1@gmail.com \
--cc=tmaimon77@gmail.com \
--cc=tony.luck@intel.com \
--cc=venture@google.com \
--cc=yuenn@google.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 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.