Linux SOC development
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Christoph Hellwig <hch@lst.de>
Cc: linux-riscv@lists.infradead.org, geert+renesas@glider.be,
	paul.walmsley@sifive.com, palmer@dabbelt.com,
	conor.dooley@microchip.com, soc@kernel.org, lkp@intel.com
Subject: Re: [PATCH] riscv: split cache ops out of dma-noncoherent.c
Date: Tue, 07 Nov 2023 23:00:25 +0000	[thread overview]
Message-ID: <169939802563.13989.11221293353672804460.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231028155101.1039049-1-hch@lst.de>

Hello:

This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Sat, 28 Oct 2023 17:51:01 +0200 you wrote:
> The cache ops are also used by the pmem code which is unconditionally
> built into the kernel.  Move them into a separate file that is built
> based on the correct config option.
> 
> Fixes: fd962781270e ("riscv: RISCV_NONSTANDARD_CACHE_OPS shouldn't depend on RISCV_DMA_NONCOHERENT")
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> 
> [...]

Here is the summary with links:
  - riscv: split cache ops out of dma-noncoherent.c
    https://git.kernel.org/riscv/c/946bb33d3302

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



  parent reply	other threads:[~2023-11-07 23:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-28 15:51 [PATCH] riscv: split cache ops out of dma-noncoherent.c Christoph Hellwig
2023-11-01 12:17 ` Conor Dooley
2023-11-01 16:54 ` Lad, Prabhakar
2023-11-07 23:00 ` patchwork-bot+linux-riscv [this message]
2023-12-06 16:19 ` patchwork-bot+linux-soc

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=169939802563.13989.11221293353672804460.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=conor.dooley@microchip.com \
    --cc=geert+renesas@glider.be \
    --cc=hch@lst.de \
    --cc=linux-riscv@lists.infradead.org \
    --cc=lkp@intel.com \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=soc@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