From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Christian Brauner <brauner@kernel.org>,
Kent Overstreet <kent.overstreet@linux.dev>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the vfs-brauner tree with the bcachefs tree
Date: Tue, 12 Mar 2024 14:56:32 +1100 [thread overview]
Message-ID: <20240312145632.61aa94b3@canb.auug.org.au> (raw)
In-Reply-To: <20240226111257.2784c310@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1602 bytes --]
Hi all,
On Mon, 26 Feb 2024 11:12:57 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the vfs-brauner tree got a conflict in:
>
> fs/bcachefs/super-io.c
>
> between commit:
>
> 2881c58d14b6 ("bcachefs: bch2_print_opts()")
>
> from the bcachefs tree and commit:
>
> 9f2f767f5ef8 ("bcachefs: port block device access to file")
>
> from the vfs-brauner 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.
>
> --
> Cheers,
> Stephen Rothwell
>
> diff --cc fs/bcachefs/super-io.c
> index 38a5073202c5,bd64eb68e84a..000000000000
> --- a/fs/bcachefs/super-io.c
> +++ b/fs/bcachefs/super-io.c
> @@@ -715,12 -715,11 +715,12 @@@ retry
> opt_set(*opts, nochanges, true);
> }
>
> - if (IS_ERR(sb->bdev_handle)) {
> - ret = PTR_ERR(sb->bdev_handle);
> + if (IS_ERR(sb->s_bdev_file)) {
> + ret = PTR_ERR(sb->s_bdev_file);
> + prt_printf(&err, "error opening %s: %s", path, bch2_err_str(ret));
> goto err;
> }
> - sb->bdev = sb->bdev_handle->bdev;
> + sb->bdev = file_bdev(sb->s_bdev_file);
>
> ret = bch2_sb_realloc(sb, 0);
> if (ret) {
This is now a conflict between the bcachefs tree and Linus' tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-03-12 3:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 0:12 linux-next: manual merge of the vfs-brauner tree with the bcachefs tree Stephen Rothwell
2024-03-12 3:56 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-17 16:55 Mark Brown
2024-02-14 23:05 Stephen Rothwell
2024-02-12 23:04 Stephen Rothwell
2023-10-25 23:01 Stephen Rothwell
2023-10-26 5:16 ` Amir Goldstein
2023-10-26 18:35 ` Kent Overstreet
2023-10-26 19:34 ` Amir Goldstein
2023-10-26 20:37 ` Kent Overstreet
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=20240312145632.61aa94b3@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=brauner@kernel.org \
--cc=kent.overstreet@linux.dev \
--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