From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Christian Brauner <brauner@kernel.org>,
Trond Myklebust <trondmy@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Sagi Grimberg <sagi@grimberg.me>,
Trond Myklebust <trond.myklebust@hammerspace.com>
Subject: linux-next: manual merge of the vfs-brauner tree with the nfs tree
Date: Tue, 4 Jun 2024 10:12:09 +1000 [thread overview]
Message-ID: <20240604101209.5134a47c@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 766 bytes --]
Hi all,
Today's linux-next merge of the vfs-brauner tree got a conflict in:
fs/nfs/symlink.c
between commit:
134d0b3f2440 ("nfs: propagate readlink errors in nfs_symlink_filler")
from the nfs tree and commit:
8f3ab6e4bebe ("nfs: Remove calls to folio_set_error")
from the vfs-brauner tree.
I fixed it up (the latter included the change from thr former) 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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2024-06-04 0:12 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=20240604101209.5134a47c@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 \
--cc=sagi@grimberg.me \
--cc=trond.myklebust@hammerspace.com \
--cc=trondmy@gmail.com \
--cc=willy@infradead.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
all inboxes | Powered by JetHome®