From: Jeff Layton <jlayton@redhat.com>
To: NeilBrown <neilb@suse.com>,
Anna Schumaker <Anna.Schumaker@netapp.com>,
Trond Myklebust <trond.myklebust@primarydata.com>
Cc: Benjamin Coddington <bcodding@redhat.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
Bruce Fields <bfields@fieldses.org>,
Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [PATCH 3/5] NFSv4: change nfs4_select_rw_stateid to take a lock_context inplace of lock_owner
Date: Tue, 25 Oct 2016 15:49:31 -0400 [thread overview]
Message-ID: <1477424971.2654.14.camel@redhat.com> (raw)
In-Reply-To: <87bmyo28tb.fsf@notabene.neil.brown.name>
On Thu, 2016-10-13 at 15:04 +1100, NeilBrown wrote:
> On Thu, Oct 13 2016, Anna Schumaker wrote:
> >
> > >
> > >
> > > Also, as a side note: There were some changes around the NFS file
> > > locking code that went into the CB_NOTIFY_LOCK patches. Those are in
> > > linux-next now, and I _think_ Anna is going to merge them for v4.9. I
> > > don't see any obvious conflicts here, but you may want to ensure that
> > > you're basing this on top of linux-next to minimize them.
> >
> > Yep, they'll be in 4.9. Updating against those changes wouldn't hurt :)
>
> Ok....
> I note that
> git://git.linux-nfs.org/projects/anna/linux-nfs.git#linux-next
>
> isn't in
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
>
> Should it be?
>
> NeilBrown
Yes, it seems like that should be going into -next.
Anna, do you and Trond have something worked out where the patches in
your pull requests are going into -next through Trond's tree?
--
Jeff Layton <jlayton@redhat.com>
next prev parent reply other threads:[~2016-10-25 19:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 2:39 [PATCH 0/5] NFSv4: Fix stateid used when flock locks in use NeilBrown
2016-10-12 2:39 ` [PATCH 4/5] NFSv4: enhance nfs4_copy_lock_stateid to use a flock stateid if there is one NeilBrown
2016-10-12 2:39 ` [PATCH 1/5] NFS: remove l_pid field from nfs_lockowner NeilBrown
2016-10-12 11:28 ` Jeff Layton
2016-10-12 22:59 ` NeilBrown
2016-10-12 2:39 ` [PATCH 3/5] NFSv4: change nfs4_select_rw_stateid to take a lock_context inplace of lock_owner NeilBrown
2016-10-12 12:33 ` Jeff Layton
2016-10-12 13:48 ` Anna Schumaker
2016-10-13 4:04 ` NeilBrown
2016-10-25 19:49 ` Jeff Layton [this message]
2016-10-13 4:15 ` NeilBrown
2016-10-12 2:39 ` [PATCH 2/5] NFSv4: add flock_owner to open context NeilBrown
2016-10-12 3:33 ` [PATCH 2/5 - version 2] " NeilBrown
2016-10-12 11:32 ` Jeff Layton
2016-10-12 2:39 ` [PATCH 5/5] NFS: discard nfs_lockowner structure NeilBrown
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=1477424971.2654.14.camel@redhat.com \
--to=jlayton@redhat.com \
--cc=Anna.Schumaker@netapp.com \
--cc=bcodding@redhat.com \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.com \
--cc=trond.myklebust@primarydata.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.