public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Andrea Parri <parri.andrea@gmail.com>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
	palmer@dabbelt.com, aou@eecs.berkeley.edu,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] riscv,mmio: I/O barriers fixes and cleanups
Date: Wed, 09 Aug 2023 14:40:21 +0000	[thread overview]
Message-ID: <169159202106.17533.2222118881302041934.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230711133348.151383-1-parri.andrea@gmail.com>

Hello:

This series was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Tue, 11 Jul 2023 15:33:46 +0200 you wrote:
> Andrea Parri (2):
>   riscv,mmio: Fix readX()-to-delay() ordering
>   riscv,mmio: Use the generic implementation for the I/O accesses
> 
>  arch/riscv/include/asm/mmio.h | 72 ++++-------------------------------
>  1 file changed, 8 insertions(+), 64 deletions(-)

Here is the summary with links:
  - [1/2] riscv,mmio: Fix readX()-to-delay() ordering
    https://git.kernel.org/riscv/c/4eb2eb1b4c0e
  - [2/2] riscv,mmio: Use the generic implementation for the I/O accesses
    (no matching commit)

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



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

      parent reply	other threads:[~2023-08-09 14:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-11 13:33 [PATCH 0/2] riscv,mmio: I/O barriers fixes and cleanups Andrea Parri
2023-07-11 13:33 ` [PATCH 1/2] riscv,mmio: Fix readX()-to-delay() ordering Andrea Parri
2023-07-11 13:33 ` [PATCH 2/2] riscv,mmio: Use the generic implementation for the I/O accesses Andrea Parri
2023-07-12  7:05   ` Conor Dooley
2023-07-12 15:18     ` Andrea Parri
2023-08-09 14:40 ` patchwork-bot+linux-riscv [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=169159202106.17533.2222118881302041934.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=parri.andrea@gmail.com \
    --cc=paul.walmsley@sifive.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