All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: mm-commits@vger.kernel.org, paul.walmsley@sifive.com,
	palmer@dabbelt.com, ldv@strace.io, charlie@rivosinc.com,
	aou@eecs.berkeley.edu, alex@ghiti.fr
Subject: Re: + syscallh-add-syscall_set_arguments-fix.patch added to mm-new branch
Date: Thu, 10 Apr 2025 19:47:26 -0700	[thread overview]
Message-ID: <20250411024726.GA2717907@ax162> (raw)
In-Reply-To: <20250411014303.CF55AC4CEDD@smtp.kernel.org>

Hi Andrew,

On Thu, Apr 10, 2025 at 06:43:03PM -0700, Andrew Morton wrote:
> 
> The patch titled
>      Subject: riscv: avoid fortify warning in syscall_get_arguments()
> has been added to the -mm mm-new branch.  Its filename is
>      syscallh-add-syscall_set_arguments-fix.patch
...
> ------------------------------------------------------
> From: Nathan Chancellor <nathan@kernel.org>
> Subject: riscv: avoid fortify warning in syscall_get_arguments()

I do not think I made myself clear enough in my request when reading it
back, so I do apologize for that. I need the diff at the end of [1]
applied to syscallh-add-syscall_set_arguments.patch, not [2], which is a
standalone patch for the existing syscall_get_arguments() that should go
via the RISC-V tree because it is an existing issue (or at least be kept
in standalone patch form).

[1]: https://lore.kernel.org/20250408213131.GA2872426@ax162/
[2]: https://lore.kernel.org/20250409-riscv-avoid-fortify-warning-syscall_get_arguments-v1-1-7853436d4755@kernel.org/

Cheers,
Nathan

  reply	other threads:[~2025-04-11  2:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-11  1:43 + syscallh-add-syscall_set_arguments-fix.patch added to mm-new branch Andrew Morton
2025-04-11  2:47 ` Nathan Chancellor [this message]
2025-04-11  4:06   ` Andrew Morton
2025-04-11 14:47     ` Nathan Chancellor
  -- strict thread matches above, loose matches on Subject: below --
2025-04-11  3:56 Andrew Morton

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=20250411024726.GA2717907@ax162 \
    --to=nathan@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=charlie@rivosinc.com \
    --cc=ldv@strace.io \
    --cc=mm-commits@vger.kernel.org \
    --cc=palmer@dabbelt.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 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.