mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Jeff Layton <jlayton@kernel.org>, Ilya Dryomov <idryomov@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Tal Zussman <tz2294@columbia.edu>, Zi Yan <ziy@nvidia.com>
Subject: linux-next: manual merge of the ceph tree with the origin tree
Date: Wed, 28 Oct 2026 12:09:36 +0000	[thread overview]
Message-ID: <auHmABrM3hZnrSVf@sirena.org.uk> (raw)

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

Hi all,

FIXME: Add author(s)/SOB of conflicting commits.

Today's linux-next merge of the ceph tree got a conflict in:

  fs/ceph/addr.c

between commit:

  6d1a85b306729 ("ceph: replace PagePrivate() with page_private()")

from the origin tree and commit:

  81a949790a690 ("ceph: add ceph_folio_snap_context()")

from the ceph tree.

I fixed it up (see below) 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.

diff --cc fs/ceph/addr.c
index 21d52d8498424,259e317981558..0000000000000
--- a/fs/ceph/addr.c
+++ b/fs/ceph/addr.c
@@@ -65,12 -65,13 +65,13 @@@
  	(CONGESTION_ON_THRESH(congestion_kb) -				\
  	 (CONGESTION_ON_THRESH(congestion_kb) >> 2))
  
 -static int ceph_netfs_check_write_begin(struct file *file, loff_t pos, unsigned int len,
 +static int ceph_netfs_check_write_begin(struct file *file, uoff_t pos, unsigned int len,
  					struct folio **foliop, void **_fsdata);
  
- static inline struct ceph_snap_context *page_snap_context(struct page *page)
+ static inline
+ struct ceph_snap_context *ceph_folio_snap_context(const struct folio *folio)
  {
- 	return (void *)page_private(page);
+ 	return folio->private;
  }
  
  /*

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

                 reply	other threads:[~2026-10-28 12:09 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=auHmABrM3hZnrSVf@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=idryomov@gmail.com \
    --cc=jlayton@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=tz2294@columbia.edu \
    --cc=ziy@nvidia.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®