From: "J. Bruce Fields" <bfields@fieldses•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Al Viro <viro@ZenIV•linux.org.uk>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
NeilBrown <neilb@suse•de>
Subject: Re: linux-next: manual merge of the vfs tree with the nsfd tree
Date: Sun, 10 Jan 2016 21:59:18 -0500 [thread overview]
Message-ID: <20160111025918.GB25396@fieldses.org> (raw)
In-Reply-To: <20160111121632.26fd5873@canb.auug.org.au>
On Mon, Jan 11, 2016 at 12:16:32PM +1100, Stephen Rothwell wrote:
> Today's linux-next merge of the vfs tree got a conflict in:
>
> fs/namei.c
>
> between commit:
>
> 1932ac9d7cef ("nfsd: don't hold i_mutex over userspace upcalls")
>
> from the nfsd tree and commit:
>
> bbddca8e8fac ("nfsd: don't hold i_mutex over userspace upcalls")
>
> from the vfs tree.
>
> Similar patch, but slightly different. :-(
>
> I fixed it up (I used the vfs tree version) and can carry the fix as
> necessary (no action is required).
Thanks, I've dropped my version.
--b.
prev parent reply other threads:[~2016-01-11 2:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 1:16 linux-next: manual merge of the vfs tree with the nsfd tree Stephen Rothwell
2016-01-11 2:59 ` J. Bruce Fields [this message]
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=20160111025918.GB25396@fieldses.org \
--to=bfields@fieldses$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=neilb@suse$(echo .)de \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=viro@ZenIV$(echo .)linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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