From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Steve French <smfrench@gmail.com>
Cc: Jens Axboe <axboe@kernel.dk>, CIFS <linux-cifs@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>,
David Howells <dhowells@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Steve French <stfrench@microsoft.com>
Subject: Re: linux-next: manual merge of the block tree with the cifs tree
Date: Tue, 21 Feb 2023 11:37:56 +1100 [thread overview]
Message-ID: <20230221113756.70d8359d@canb.auug.org.au> (raw)
In-Reply-To: <20230220114201.11659a37@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1023 bytes --]
Hi all,
On Mon, 20 Feb 2023 11:42:01 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the block tree got conflicts in:
>
> fs/cifs/fscache.c
>
> between commit:
>
> 8378eea2e41f ("cifs: Change the I/O paths to use an iterator rather than a page list")
>
> from the cifs tree and commit:
>
> 220ae4a5c2ba ("cifs: use bvec_set_page to initialize bvecs")
>
> from the block tree.
>
> I fixed it up (the former removed the code updated by the latter in
> fscache_fallback_write_pages(), so I did that) 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.
This is now a conflict between the cifs 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:[~2023-02-21 0:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 0:42 linux-next: manual merge of the block tree with the cifs tree Stephen Rothwell
2023-02-21 0:37 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-20 0:50 Stephen Rothwell
2023-02-21 0:39 ` Stephen Rothwell
2023-02-21 0:47 ` Steve French
2023-02-20 0:46 Stephen Rothwell
2023-02-21 0:38 ` Stephen Rothwell
2023-02-20 0:33 Stephen Rothwell
2023-02-20 0:21 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=20230221113756.70d8359d@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=axboe@kernel.dk \
--cc=dhowells@redhat.com \
--cc=hch@lst.de \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=smfrench@gmail.com \
--cc=stfrench@microsoft.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