mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Jens Axboe" <axboe@kernel.dk>, "Peter Zijlstra" <peterz@infradead.org>
Cc: "Stephen Rothwell" <sfr@canb.auug.org.au>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	linux-next <linux-next@vger.kernel.org>,
	"Sohil Mehta" <sohil.mehta@intel.com>
Subject: Re: linux-next: manual merge of the block tree with the asm-generic tree
Date: Mon, 09 Oct 2023 16:21:54 +0200	[thread overview]
Message-ID: <af82e327-5d80-4031-a1a7-a275bed8e248@app.fastmail.com> (raw)
In-Reply-To: <b7c57f03-4606-4190-98c5-344c49656f9c@kernel.dk>

On Mon, Oct 9, 2023, at 16:16, Jens Axboe wrote:
> On 10/9/23 8:13 AM, Peter Zijlstra wrote:
>> On Mon, Oct 09, 2023 at 11:00:19AM +0200, Arnd Bergmann wrote:
>>>
>>> Let's not make it worse for now. All the numbers since the
>>> introduction of the time64 syscalls are offset by exactly 120
>>> on alpha, and I'd prefer to keep it that way for the moment.
>>>
>>> I still hope to eventually finish the conversion of all architectures
>>> to a single syscall.tbl for numbers >400, and if that happens before
>>> the end of alpha, a different ordering would just be extra pain.
>> 
>> Fair enough; should we look at rebase those futex patches for this? (bit
>> of a pain as that would also mean rebasing block)
>
> From my point of view, this isn't a huge problem if we do it now. The
> io_uring-futex branch is a separate branch and I have nothing on top of
> it, so I could easily just re-pull your updated branch and rebase my
> changes on top.
>
>> Or do we want to keep this fixup in the merge resolution and make sure
>> Linus is aware?
>
> If you're OK with it, I'd say let's rebase and save ourselves the
> trouble at merge time.

Sounds good, thanks.

If it's any help, I can also merge the patches that wire up the
syscalls through the asm-generic tree to avoid the conflicts
altogether.

     Arnd

  reply	other threads:[~2023-10-09 14:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-09  1:31 Stephen Rothwell
2023-10-09  8:48 ` Peter Zijlstra
2023-10-09  9:00   ` Arnd Bergmann
2023-10-09 14:13     ` Peter Zijlstra
2023-10-09 14:16       ` Jens Axboe
2023-10-09 14:21         ` Arnd Bergmann [this message]
2023-10-11 16:21         ` Jens Axboe
2023-10-11 17:54           ` Peter Zijlstra
2023-10-11 21:32             ` Ingo Molnar
2023-10-11 21:42               ` Jens Axboe
2023-10-11 22:01                 ` Ingo Molnar
2023-10-16 11:53                   ` Ingo Molnar
2023-10-17  1:12                     ` Stephen Rothwell
2023-10-16 11:31     ` [tip: locking/core] alpha: Fix up new futex syscall numbers tip-bot2 for Peter Zijlstra
2023-10-09  9:33   ` linux-next: manual merge of the block tree with the asm-generic tree Stephen Rothwell
2023-10-31 22:21 ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2023-09-25  2:05 Stephen Rothwell
2023-09-25  2:09 ` Stephen Rothwell
2023-10-31 22:23   ` Stephen Rothwell

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=af82e327-5d80-4031-a1a7-a275bed8e248@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=axboe@kernel.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=sfr@canb.auug.org.au \
    --cc=sohil.mehta@intel.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

all inboxes | Powered by JetHome®