From: "J. Bruce Fields" <bfields@redhat.com>
To: Olga Kornievskaia <aglo@umich.edu>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
Olga Kornievskaia <kolga@netapp.com>,
linux-nfs <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH v10 0/9] NFSD support for async COPY
Date: Wed, 5 Sep 2018 11:56:32 -0400 [thread overview]
Message-ID: <20180905155632.GA10680@parsley.fieldses.org> (raw)
In-Reply-To: <CAN-5tyEsME8YdBvzUczE6N_L3ptV8DTA0a4sZCgmDUfGX99CDA@mail.gmail.com>
On Wed, Sep 05, 2018 at 10:30:59AM -0400, Olga Kornievskaia wrote:
> finally getting back to this...
>
> On Wed, Aug 22, 2018 at 9:47 PM J. Bruce Fields <bfields@fieldses.org> wrote:
> >
> > On Thu, Aug 09, 2018 at 04:34:50PM -0400, J. Bruce Fields wrote:
> > > Thanks, I've added these to my -next branch, and I want to read through
> > > them tomorrow.
> >
> > Gah, I screwed up and took to long to get around to this and have a few
> > things I'd like to change, so I'm going to queue these up again for
> > 4.20.
> >
> > The way the patches are broken up doesn't really work; for example
> > init_cp_state is used in one but patch not defined till a later patch,
>
> I don't see what you are seeing.. init_cp_state is defined and used in
> 0006-NFSD-create-new-stateid-for-async-copy.patch
Apologies, you're right. I remember getting a compile error and
checking against the patches in my inbox to make sure the same
use-before-definition error was there. But now I can't find any
problem. That makes me wonder whether I was looking at the wrong
version of the patches or something.
I've checked my latest version against your latest and it looks OK to
me, but you might want to double check as well.
--b.
prev parent reply other threads:[~2018-09-05 20:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 22:19 [PATCH v10 0/9] NFSD support for async COPY Olga Kornievskaia
2018-07-20 22:19 ` [PATCH v10 1/9] NFSD CB_OFFLOAD xdr Olga Kornievskaia
2018-07-20 22:19 ` [PATCH v10 2/9] NFSD OFFLOAD_STATUS xdr Olga Kornievskaia
2018-07-20 22:19 ` [PATCH v10 3/9] NFSD OFFLOAD_CANCEL xdr Olga Kornievskaia
2018-07-20 22:19 ` [PATCH v10 4/9] NFSD xdr callback stateid in async COPY reply Olga Kornievskaia
2018-07-20 22:19 ` [PATCH v10 5/9] NFSD introduce async copy feature Olga Kornievskaia
2018-07-20 22:19 ` [PATCH v10 6/9] NFSD create new stateid for async copy Olga Kornievskaia
2018-07-20 22:19 ` [PATCH v10 7/9] NFSD handle OFFLOAD_CANCEL op Olga Kornievskaia
2018-07-20 22:19 ` [PATCH v10 8/9] NFSD support OFFLOAD_STATUS Olga Kornievskaia
2018-07-20 22:19 ` [PATCH v10 9/9] NFSD stop ongoing async copies on client shutdown Olga Kornievskaia
2018-08-09 20:34 ` [PATCH v10 0/9] NFSD support for async COPY J. Bruce Fields
2018-08-23 1:47 ` J. Bruce Fields
2018-08-23 12:22 ` J. Bruce Fields
2018-08-23 12:32 ` J. Bruce Fields
2018-08-23 18:30 ` Olga Kornievskaia
2018-09-05 14:30 ` Olga Kornievskaia
2018-09-05 15:56 ` 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=20180905155632.GA10680@parsley.fieldses.org \
--to=bfields@redhat.com \
--cc=aglo@umich.edu \
--cc=bfields@fieldses.org \
--cc=kolga@netapp.com \
--cc=linux-nfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).