public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
	"Christian Brauner" <brauner@kernel.org>,
	"Steven Rostedt" <rostedt@goodmis.org>,
	"Masami Hiramatsu" <mhiramat@kernel.org>,
	"Christian Göttsche" <cgzones@googlemail.com>,
	"Jiri Olsa" <jolsa@kernel.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Linux Next Mailing List" <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the random tree with the vfs-brauner, ftrace trees
Date: Wed, 3 Jul 2024 03:07:32 +1000	[thread overview]
Message-ID: <20240703030732.02b5dda7@canb.auug.org.au> (raw)
In-Reply-To: <CAHmME9rYfTtO9CPGi1nB=ohZ_SBMFocxpB=Ga3cqA54EF8F7Og@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]

Hi Jason,

On Tue, 2 Jul 2024 16:43:17 +0200 "Jason A. Donenfeld" <Jason@zx2c4.com> wrote:
>
> Hi Stephen,
> 
> On Tue, Jul 2, 2024 at 8:56 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >  +466   n32     removexattrat                   sys_removexattrat
> > ++468   n32     vgetrandom_alloc                sys_vgetrandom_alloc  
> 
> Wondering why 467 was skipped.

It is being used by the uretprobe system call on x86 and asm-generic.

> Also, any chance you can let me keep 463 and shift the others (unless
> Christian objects)? Or does it not really matter anyway because Linus
> is gonna merge this how he wants, separately from what you do in
> -next?

Well, the other new syscalls have been in -next for some time, so I
don't really want to move them (and it would make more work for me :-)).

As you say, Linus will just merge these depending on his own ordering.
However, if you switch to 468/568, then he will probably not change it.
I was also hoping that the uretprobe syscall would change to 467 for
the same reason.
-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2024-07-02 17:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-02  6:56 linux-next: manual merge of the random tree with the vfs-brauner, ftrace trees Stephen Rothwell
2024-07-02 14:43 ` Jason A. Donenfeld
2024-07-02 17:07   ` Stephen Rothwell [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=20240703030732.02b5dda7@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=Jason@zx2c4.com \
    --cc=brauner@kernel.org \
    --cc=cgzones@googlemail.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tytso@mit.edu \
    /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