From: James Morse <james.morse@arm.com>
To: Lei Wang <leiwang_git@outlook.com>
Cc: Borislav Petkov <bp@alien8.de>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mchehab@kernel.org" <mchehab@kernel.org>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"sashal@kernel.org" <sashal@kernel.org>,
"hangl@microsoft.com" <hangl@microsoft.com>,
"lewan@microsoft.com" <lewan@microsoft.com>,
"ruizhao@microsoft.com" <ruizhao@microsoft.com>,
"scott.branden@broadcom.com" <scott.branden@broadcom.com>,
"yuqing.shen@broadcom.com" <yuqing.shen@broadcom.com>,
"ray.jui@broadcom.com" <ray.jui@broadcom.com>
Subject: Re: [PATCH v6 1/2] dt-bindings: edac: arm-dmc520.txt
Date: Mon, 21 Oct 2019 17:43:42 +0100 [thread overview]
Message-ID: <1ae9a840-d5b6-ccd6-8481-d43665b4411b@arm.com> (raw)
In-Reply-To: <BY5PR04MB65996A0CEB37001C763B248C866C0@BY5PR04MB6599.namprd04.prod.outlook.com>
Hi Lei,
On 18/10/2019 21:08, Lei Wang wrote:
> This thread hasn't got traction from DT owners.
It looks like your patches didn't make it to the mailing list:
https://lore.kernel.org/r/BY5PR04MB6599EAA659A53B2331CB812586890@BY5PR04MB6599.namprd04.prod.outlook.com
You can search on https://lore.kernel.org/linux-edac/, I can only see the replies from the
people who received it directly.
I can't see anything obvious in the headers that would cause it to get rejected. Did you
get any bounces/errors from the list?
Depending on how the DT folk work, this may be why you haven't had a response yet. Tools
like patchwork will depend on the message reaching the list.
> James did give ACK before.
> Should that be good enough?
Nope! You need someone from the maintainer's entry for those files to review it.
I gave my R-B as what you'd done made sense from the TRM and the driver. The DT folk will
have a wider view and may have some advice.
Thanks,
James
next prev parent reply other threads:[~2019-10-21 16:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BY5PR04MB6599EAA659A53B2331CB812586890@BY5PR04MB6599.namprd04.prod.outlook.com>
2019-09-23 16:10 ` Borislav Petkov
[not found] ` <e2b9cd68-abaa-bdcd-cc56-cca285272569@outlook.com>
[not found] ` <41637032-a308-9a92-1b49-cb51af2580f8@outlook.com>
[not found] ` <BY5PR04MB65996A0CEB37001C763B248C866C0@BY5PR04MB6599.namprd04.prod.outlook.com>
2019-10-21 16:43 ` James Morse [this message]
[not found] ` <BY5PR04MB659953E22E846D0BF4384D0086690@BY5PR04MB6599.namprd04.prod.outlook.com>
2019-10-22 12:33 ` Borislav Petkov
2019-10-23 13:22 ` James Morse
2019-10-23 15:22 ` Rob Herring
2019-10-23 15:37 ` Rob Herring
2019-10-25 17:31 ` Lei Wang
2019-11-01 21:30 ` Lei Wang
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=1ae9a840-d5b6-ccd6-8481-d43665b4411b@arm.com \
--to=james.morse@arm.com \
--cc=bp@alien8.de \
--cc=devicetree@vger.kernel.org \
--cc=hangl@microsoft.com \
--cc=leiwang_git@outlook.com \
--cc=lewan@microsoft.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=ray.jui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=ruizhao@microsoft.com \
--cc=sashal@kernel.org \
--cc=scott.branden@broadcom.com \
--cc=yuqing.shen@broadcom.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
all inboxes | Powered by JetHome®