public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@amd.com>
To: Palmer Dabbelt <palmer@dabbelt.com>, Conor Dooley <conor@kernel.org>
Cc: linux-kernel@vger.kernel.org, monstr@monstr.eu,
	michal.simek@xilinx.com, git@xilinx.com, aou@eecs.berkeley.edu,
	krzysztof.kozlowski+dt@linaro.org,
	Paul Walmsley <paul.walmsley@sifive.com>,
	robh+dt@kernel.org, devicetree@vger.kernel.org,
	linux-riscv@lists.infradead.org
Subject: Re: [PATCH] dt-bindings: riscv: cpus: Add AMD MicroBlaze V compatible
Date: Fri, 5 Jan 2024 15:44:48 +0100	[thread overview]
Message-ID: <e35a446c-ab18-452b-9d44-b73ce3ca3856@amd.com> (raw)
In-Reply-To: <mhng-78b77d96-e318-45f5-9032-4a1bee73afcd@palmer-ri-x1c9a>



On 12/20/23 16:15, Palmer Dabbelt wrote:
> On Thu, 09 Nov 2023 09:15:09 PST (-0800), Conor Dooley wrote:
>> On Mon, Nov 06, 2023 at 12:37:47PM +0100, Michal Simek wrote:
>>> MicroBlaze V is new AMD/Xilinx soft-core 32bit RISC-V processor IP.
>>> It is hardware compatible with classic MicroBlaze processor.
>>>
>>> Signed-off-by: Michal Simek <michal.simek@amd.com>
>>
>> Acked-by: Conor Dooley <conor.dooley@microchip.com>
>> I thought I had already done so, but must have forgot to actually send
>> the email.
> 
> Conor asked me to pick it up, it's over staged for testing.  Pretty much
> no chance it fails anything, so should show up on for-next soon.

Palmer: Any update on this?

Thanks,
Michal

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2024-01-05 14:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-06 11:37 [PATCH] dt-bindings: riscv: cpus: Add AMD MicroBlaze V compatible Michal Simek
2023-11-08 17:12 ` Rob Herring
2023-11-08 18:35   ` Keryell, Ronan (XILINX LABS)
2023-11-09 17:15 ` Conor Dooley
2023-12-20 15:15   ` Palmer Dabbelt
2024-01-05 14:44     ` Michal Simek [this message]
2023-12-20 13:50 ` Michal Simek
2024-01-05 21:50 ` patchwork-bot+linux-riscv

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=e35a446c-ab18-452b-9d44-b73ce3ca3856@amd.com \
    --to=michal.simek@amd.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=git@xilinx.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=michal.simek@xilinx.com \
    --cc=monstr@monstr.eu \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.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