public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Christian Brauner <brauner@kernel.org>,
	David Chinner <david@fromorbit.com>,
	Carlos Maiolino <cem@kernel.org>,
	"Darrick J. Wong" <djwong@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>, <linux-xfs@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 vfs-brauner tree
Date: Wed, 16 Oct 2024 09:02:20 +1100	[thread overview]
Message-ID: <20241016090220.5b67bb5f@canb.auug.org.au> (raw)

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

Hi all,

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

  c650b5a9028f ("xfs: punch delalloc extents from the COW fork for COW writes")
  f8bb8ce211ce ("xfs: set IOMAP_F_SHARED for all COW fork allocations")
  cd97b59a531d ("xfs: share more code in xfs_buffered_write_iomap_begin")
  7f6e164457c6 ("xfs: support the COW fork in xfs_bmap_punch_delalloc_range")
  99c29f16b79f ("xfs: IOMAP_ZERO and IOMAP_UNSHARE already hold invalidate_lock")
  2f58268678f1 ("xfs: take XFS_MMAPLOCK_EXCL xfs_file_write_zero_eof")
  71f1cd607850 ("xfs: factor out a xfs_file_write_zero_eof helper")
  f66815a521bd ("iomap: move locking out of iomap_write_delalloc_release")
  1eef06039a75 ("iomap: remove iomap_file_buffered_write_punch_delalloc")
  18f08714e7b2 ("iomap: factor out a iomap_last_written_block helper")

These are commits

  f6f91d290c8b ("xfs: punch delalloc extents from the COW fork for COW writes")
  7d6fe5c586e6 ("xfs: set IOMAP_F_SHARED for all COW fork allocations")
  c29440ff66d6 ("xfs: share more code in xfs_buffered_write_iomap_begin")
  8fe3b21efa07 ("xfs: support the COW fork in xfs_bmap_punch_delalloc_range")
  abd7d651ad2c ("xfs: IOMAP_ZERO and IOMAP_UNSHARE already hold invalidate_lock")
  acfbac776496 ("xfs: take XFS_MMAPLOCK_EXCL xfs_file_write_zero_eof")
  3c399374af28 ("xfs: factor out a xfs_file_write_zero_eof helper")
  b78495166264 ("iomap: move locking out of iomap_write_delalloc_release")
  caf0ea451d97 ("iomap: remove iomap_file_buffered_write_punch_delalloc")
  c0adf8c3a9bf ("iomap: factor out a iomap_last_written_block helper")

in the xfs tree.

These are causing at least one conflict due to later commits in the
vfs-brauner tree.  Maybe you could share a stable branch?

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2024-10-15 22:02 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-15 22:02 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-10-19 20:29 linux-next: duplicate patches in the vfs-brauner tree Stephen Rothwell
2025-01-20 22:20 Stephen Rothwell
2025-01-12 21:55 Stephen Rothwell
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
2024-10-20 11:08 Stephen Rothwell
2024-10-21  8:22 ` Christian Brauner
2024-07-31 23:54 Stephen Rothwell
2024-07-24 22:00 Stephen Rothwell
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
2023-12-21  0:00 Stephen Rothwell
2023-12-21 10:50 ` David Howells
2023-10-18 23:12 Stephen Rothwell
2023-10-19  5:36 ` Amir Goldstein
2023-10-19  9:18   ` Christian Brauner
2023-10-12 23:48 Stephen Rothwell
2023-10-13  6:32 ` Amir Goldstein

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=20241016090220.5b67bb5f@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=brauner@kernel.org \
    --cc=cem@kernel.org \
    --cc=david@fromorbit.com \
    --cc=djwong@kernel.org \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-xfs@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