All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Samuel Holland <samuel.holland@sifive.com>
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com,
	aou@eecs.berkeley.edu, paul.walmsley@sifive.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: Select HAVE_ARCH_USERFAULTFD_MINOR
Date: Fri, 07 Jul 2023 15:10:23 +0000	[thread overview]
Message-ID: <168874262337.15275.12046013710547039140.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230624060321.3401504-1-samuel.holland@sifive.com>

Hello:

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

On Fri, 23 Jun 2023 23:03:20 -0700 you wrote:
> This allocates the VM flag needed to support the userfaultfd minor fault
> functionality. Because the flag bit is >= bit 32, it can only be enabled
> for 64-bit kernels. See commit 7677f7fd8be7 ("userfaultfd: add minor
> fault registration mode") for more information.
> 
> Signed-off-by: Samuel Holland <samuel.holland@sifive.com>
> 
> [...]

Here is the summary with links:
  - riscv: Select HAVE_ARCH_USERFAULTFD_MINOR
    https://git.kernel.org/riscv/c/a2492ca86c98

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



WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Samuel Holland <samuel.holland@sifive.com>
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com,
	aou@eecs.berkeley.edu, paul.walmsley@sifive.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: Select HAVE_ARCH_USERFAULTFD_MINOR
Date: Fri, 07 Jul 2023 15:10:23 +0000	[thread overview]
Message-ID: <168874262337.15275.12046013710547039140.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230624060321.3401504-1-samuel.holland@sifive.com>

Hello:

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

On Fri, 23 Jun 2023 23:03:20 -0700 you wrote:
> This allocates the VM flag needed to support the userfaultfd minor fault
> functionality. Because the flag bit is >= bit 32, it can only be enabled
> for 64-bit kernels. See commit 7677f7fd8be7 ("userfaultfd: add minor
> fault registration mode") for more information.
> 
> Signed-off-by: Samuel Holland <samuel.holland@sifive.com>
> 
> [...]

Here is the summary with links:
  - riscv: Select HAVE_ARCH_USERFAULTFD_MINOR
    https://git.kernel.org/riscv/c/a2492ca86c98

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

  reply	other threads:[~2023-07-07 15:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-24  6:03 [PATCH] riscv: Select HAVE_ARCH_USERFAULTFD_MINOR Samuel Holland
2023-06-24  6:03 ` Samuel Holland
2023-07-07 15:10 ` patchwork-bot+linux-riscv [this message]
2023-07-07 15:10   ` 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=168874262337.15275.12046013710547039140.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=paul.walmsley@sifive.com \
    --cc=samuel.holland@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.