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>
Cc: 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 Linus' tree
Date: Wed, 5 Feb 2025 09:38:23 +1100	[thread overview]
Message-ID: <20250205093823.4567f09f@canb.auug.org.au> (raw)

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

Hi all,

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

  fs/dcache.c
  fs/erofs/zdata.c
  fs/gfs2/quota.c
  include/linux/lockref.h

between commits:

  4b193fa75eff ("lockref: remove lockref_put_not_zero")
  6d2868d5b6fc ("lockref: use bool for false/true returns")
  25d8060418b4 ("lockref: drop superfluous externs")
  63440d1c6dd1 ("lockref: add a lockref_init helper")
  8c32b87c4f88 ("dcache: use lockref_init for d_lockref")
  6f86f1465b59 ("erofs: use lockref_init for pcl->lockref")
  3e652eba244c ("gfs2: use lockref_init for qd_lockref")

from Linus' tree (plus further commits affecting these same files in other
trees) and commits:

  74b5da771c89 ("lockref: remove lockref_put_not_zero")
  57bd981b2db7 ("lockref: use bool for false/true returns")
  80e2823cbe59 ("lockref: drop superfluous externs")
  5f0c395edf59 ("lockref: add a lockref_init helper")
  24706068b7b6 ("dcache: use lockref_init for d_lockref")
  160a93170d53 ("erofs: use lockref_init for pcl->lockref")
  0ef3858b15e3 ("gfs2: use lockref_init for qd_lockref")

from the vfs-brauner tree.

I fixed it up (these commits are just duplicates, so I used the former
vresions of these files) 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.

Please clean up the vfs-brauner tree.

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2025-02-04 22:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-04 22:38 Stephen Rothwell [this message]
2025-02-05 10:02 ` linux-next: manual merge of the vfs-brauner tree with Linus' tree Christian Brauner
  -- strict thread matches above, loose matches on Subject: below --
2024-05-05 23:52 Stephen Rothwell
2023-12-03 23:35 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=20250205093823.4567f09f@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=brauner@kernel.org \
    --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