public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Christian Brauner <brauner@kernel•org>,
	Miklos Szeredi <miklos@szeredi•hu>,
	Amir Goldstein <amir73il@gmail•com>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: duplicate patches in the vfs-brauner tree
Date: Fri, 13 Oct 2023 10:48:16 +1100	[thread overview]
Message-ID: <20231013104816.103ea713@canb.auug.org.au> (raw)

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

Hi all,

The following commits are also in the overlayfs tree as different commits
(but the same patches):

  149f455798a6 ("smb: move cifs_xattr_handlers to .rodata")
  295d3c441226 ("net: move sockfs_xattr_handlers to .rodata")
  2f5028604f08 ("shmem: move shmem_xattr_handlers to .rodata")
  375aa21d36ee ("xfs: move xfs_xattr_handlers to .rodata")
  3d649a4a832e ("overlayfs: move xattr tables to .rodata")
  c08a831c74f0 ("squashfs: move squashfs_xattr_handlers to .rodata")
  c25308c326db ("ubifs: move ubifs_xattr_handlers to .rodata")

Looks like the overlatfs tree has merged a previous verion of a topic
branch from the vfs-brauner tree.

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2023-10-12 23:48 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-12 23:48 Stephen Rothwell [this message]
2023-10-13  6:32 ` linux-next: duplicate patches in the vfs-brauner tree Amir Goldstein
  -- strict thread matches above, loose matches on Subject: below --
2023-10-18 23:12 Stephen Rothwell
2023-10-19  5:36 ` Amir Goldstein
2023-10-19  9:18   ` Christian Brauner
2023-12-21  0:00 Stephen Rothwell
2023-12-21 10:50 ` David Howells
2024-04-03 23:10 Stephen Rothwell
2024-04-03 23:59 ` Dominique Martinet
2024-04-04  0:21   ` Randy Dunlap
2024-04-04  1:44     ` Dominique Martinet
2024-04-05 10:57       ` Christian Brauner
2024-04-05 11:30         ` Dominique Martinet
2024-04-05 13:09           ` Christian Brauner
2024-04-04  2:09 ` Andrew Morton
2024-07-24 22:00 Stephen Rothwell
2024-07-31 23:54 Stephen Rothwell
2024-10-15 22:02 Stephen Rothwell
2024-10-20 11:08 Stephen Rothwell
2024-10-21  8:22 ` Christian Brauner
2025-01-05 23:10 Stephen Rothwell
2025-01-07  3:14 ` Andrew Morton
2025-01-10 11:08   ` Christian Brauner
2025-01-11  0:31     ` Andrew Morton
2025-01-12 21:55 Stephen Rothwell
2025-01-20 22:20 Stephen Rothwell
2025-10-19 20:29 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=20231013104816.103ea713@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=amir73il@gmail$(echo .)com \
    --cc=brauner@kernel$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=miklos@szeredi$(echo .)hu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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