Re: [PATCH 5 3/4] nfsd_open(): rename 'int access' to 'int may_flags' in nfsd_open()
From: Ted Ts'o <tytso@mit.edu>
Date: 2012-03-06 15:18:16
Also in:
linux-fsdevel, linux-nfs
Possibly related (same subject, not in this thread)
- 2012-04-12 · Re: [PATCH 5 3/4] nfsd_open(): rename 'int access' to 'int may_flags' in nfsd_open() · J. Bruce Fields <hidden>
- 2012-04-12 · Re: [PATCH 5 3/4] nfsd_open(): rename 'int access' to 'int may_flags' in nfsd_open() · Bernd Schubert <hidden>
- 2012-04-12 · Re: [PATCH 5 3/4] nfsd_open(): rename 'int access' to 'int may_flags' in nfsd_open() · J. Bruce Fields <hidden>
- 2012-03-20 · Re: [PATCH 5 3/4] nfsd_open(): rename 'int access' to 'int may_flags' in nfsd_open() · Ted Ts'o <hidden>
- 2012-03-19 · Re: [PATCH 5 3/4] nfsd_open(): rename 'int access' to 'int may_flags' in nfsd_open() · J. Bruce Fields <hidden>
On Mon, Mar 05, 2012 at 09:08:19PM -0500, J. Bruce Fields wrote:
Yes, that would be fine. (There may well be some conflict: simplest might be if you can get that pushed out to a stable public branch somewhere, hopefully before the merge window opens, and that'll give me a chance to pull it and handle any merge conflicts.
Are the commits you're worried about on the NFS side already in
linux-next? If so, I'll do a quick test merge and see if there are
any conflicts. If so, I'll segregate out these patches into a
separate pre-merge branch --- and then if you like you could pull them
into your branch and we can deal with it that way.
- Ted