From: "Rao, Appana Durga Kedareswara" <appanad@amd.com>
To: Greg KH <gregkh@linuxfoundation.org>,
Appana Durga Kedareswara rao
<appana.durga.kedareswara.rao@amd.com>
Cc: <robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<appana.durga.rao@xilinx.com>, <michal.simek@xilinx.com>,
<derek.kiernan@xilinx.com>, <dragan.cvetic@xilinx.com>,
<arnd@arndb.de>, <linux-arm-kernel@lists.infradead.org>,
<git@amd.com>
Subject: Re: [RESEND PATCH v5 0/4] drivers: misc: Add support for TMR Manager and Inject IPs
Date: Fri, 28 Oct 2022 14:53:06 +0530 [thread overview]
Message-ID: <6a55f582-76ac-3260-6b8b-704f92647d0e@amd.com> (raw)
In-Reply-To: <Y1ucPco2aRbQWfK1@kroah.com>
Hi Greg,
On 28/10/22 2:39 pm, Greg KH wrote:
> On Fri, Oct 28, 2022 at 02:31:02PM +0530, Appana Durga Kedareswara rao wrote:
>> This patch series adds support for TMR Manager and TMR Inject IPs.
>> The TMR Manager is responsible for handling the TMR subsystem state,
>> including fault detection and error recovery. The core is triplicated
>> in each of the sub-blocks in the TMR subsystem, and provides majority
>> voting of its internal state.
>> The TMR Inject core provides functional fault injection by changing
>> selected MicroBlaze instructions, which provides the possibility to
>> verify that the TMR subsystem error detection and fault recovery logic
>> is working properly.
>>
>> For more details about TMR Manager and Inject IPs please refer PG268[1].
>>
>> [1]: https://docs.xilinx.com/r/en-US/pg268-tmr/Triple-Modular-Redundancy-TMR-v1.0-LogiCORE-IP-Product-Guide-PG268
>>
>> Appana Durga Kedareswara rao (4):
>> dt-bindings: misc: tmr-manager: Add device-tree binding for TMR
>> Manager
>> drivers: misc: Add Support for TMR Manager
>> dt-bindings: misc: tmr-inject: Add device-tree binding for TMR Inject
>> drivers: misc: Add Support for TMR Inject IP
>
> Why is this a RESEND?
>
> What happened to the first v5 series? >
Haven't received any review comments for v5 and it's been month that i
have sent v5, so rebased the patches on top of latest tree and resend.
Should i post v6 instead of RESEND?
Regards,
Kedar.
> confused,
>
> greg k-h
prev parent reply other threads:[~2022-10-28 9:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 9:01 Appana Durga Kedareswara rao
2022-10-28 9:01 ` [RESEND PATCH v5 1/4] dt-bindings: misc: tmr-manager: Add device-tree binding for TMR Manager Appana Durga Kedareswara rao
2022-10-28 9:01 ` [RESEND PATCH v5 2/4] drivers: misc: Add Support " Appana Durga Kedareswara rao
2022-10-28 9:01 ` [RESEND PATCH v5 3/4] dt-bindings: misc: tmr-inject: Add device-tree binding for TMR Inject Appana Durga Kedareswara rao
2022-10-28 9:01 ` [RESEND PATCH v5 4/4] drivers: misc: Add Support for TMR Inject IP Appana Durga Kedareswara rao
2022-10-30 7:25 ` kernel test robot
2022-10-28 9:09 ` [RESEND PATCH v5 0/4] drivers: misc: Add support for TMR Manager and Inject IPs Greg KH
2022-10-28 9:23 ` Rao, Appana Durga Kedareswara [this message]
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=6a55f582-76ac-3260-6b8b-704f92647d0e@amd.com \
--to=appanad@amd.com \
--cc=appana.durga.kedareswara.rao@amd.com \
--cc=appana.durga.rao@xilinx.com \
--cc=arnd@arndb.de \
--cc=derek.kiernan@xilinx.com \
--cc=devicetree@vger.kernel.org \
--cc=dragan.cvetic@xilinx.com \
--cc=git@amd.com \
--cc=gregkh@linuxfoundation.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=robh+dt@kernel.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
all inboxes | Powered by JetHome®