public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Daniel Borkmann <daniel@iogearbox•net>,
	Alexei Starovoitov <ast@kernel•org>,
	Andrii Nakryiko <andrii@kernel•org>,
	Christian Brauner <brauner@kernel•org>
Cc: bpf <bpf@vger•kernel.org>, Networking <netdev@vger•kernel.org>,
	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 bpf-next tree
Date: Thu, 3 Jul 2025 12:51:21 +1000	[thread overview]
Message-ID: <20250703125121.2f34c015@canb.auug.org.au> (raw)

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

Hi all,

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

  f4fba2d6d282 ("selftests/bpf: Add tests for bpf_cgroup_read_xattr")
  1504d8c7c702 ("bpf: Mark cgroup_subsys_state->cgroup RCU safe")
  535b070f4a80 ("bpf: Introduce bpf_cgroup_read_xattr to read xattr of cgroup's node")

These are commits

  21eebc655b0f ("selftests/bpf: Add tests for bpf_cgroup_read_xattr")
  5bc9557c9f17 ("bpf: Mark cgroup_subsys_state->cgroup RCU safe")
  b95ee9049c93 ("bpf: Introduce bpf_cgroup_read_xattr to read xattr of cgroup's node")

in the vfs-brauner tree.

These duplicates are causing unnecessary conflicts.

The previous commit in both trees is not quite identical.

-- 
Cheers,
Stephen Rothwell

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

                 reply	other threads:[~2025-07-03  2:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20250703125121.2f34c015@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=andrii@kernel$(echo .)org \
    --cc=ast@kernel$(echo .)org \
    --cc=bpf@vger$(echo .)kernel.org \
    --cc=brauner@kernel$(echo .)org \
    --cc=daniel@iogearbox$(echo .)net \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=netdev@vger$(echo .)kernel.org \
    /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