public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Arnd Bergmann <arnd@arndb.de>, Christian Brauner <brauner@kernel.org>
Cc: "Christian Göttsche" <cgzones@googlemail.com>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Linux Next Mailing List" <linux-next@vger.kernel.org>
Subject: linux-next: manual merge of the vfs-brauner tree with the asm-generic tree
Date: Tue, 9 Jul 2024 10:57:09 +1000	[thread overview]
Message-ID: <20240709105709.18ce785d@canb.auug.org.au> (raw)

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

Hi all,

Today's linux-next merge of the fs-next tree got conflicts in:

  arch/arm64/include/asm/unistd.h
  arch/arm64/include/asm/unistd32.h

between commit:

  ea0130bf3c45 ("arm64: convert unistd_32.h to syscall.tbl format")

from the asm-generic tree and commit:

  e6873349f700 ("fs/xattr: add *at family syscalls")

from the vfs-brauner tree.

I fixed it up (I used the former versions) and can carry the fix as
necessary. This is now fixed as far as linux-next is concerned, but any
non trivial conflicts should be mentioned to your upstream maintainer
when your tree is submitted for merging.  You may also want to consider
cooperating with the maintainer of the conflicting tree to minimise any
particularly complex conflicts.

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2024-07-09  0:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-09  0:57 Stephen Rothwell [this message]
2024-07-09 10:08 ` linux-next: manual merge of the vfs-brauner tree with the asm-generic tree Stephen Rothwell
2024-07-09 11:44   ` Arnd Bergmann
2024-07-09 11:53     ` Jiri Olsa
2024-07-09 12:20       ` Arnd Bergmann
2024-07-09 12:42         ` Jiri Olsa
2024-07-09 12:58           ` Arnd Bergmann
2024-07-09 13:17             ` Jiri Olsa
2024-07-09 14:26               ` Arnd Bergmann
2024-07-10  2:22     ` 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=20240709105709.18ce785d@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=arnd@arndb.de \
    --cc=brauner@kernel.org \
    --cc=cgzones@googlemail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.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