All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Disseldorp <ddiss@suse.de>
To: David Drysdale <drysdale@google.com>
Cc: fstests@vger.kernel.org, linux-cifs@vger.kernel.org
Subject: Re: [PATCH 2/2] cifs: add server-side copy sanity test
Date: Mon, 15 Dec 2014 11:04:31 +0100	[thread overview]
Message-ID: <20141215110431.65c8bd80@plati.site> (raw)
In-Reply-To: <CAHse=S91DYDaevHeFa51k2PAgHzoWO68QmGZrC7RNQ4Dm1Pojw@mail.gmail.com>

On Mon, 15 Dec 2014 09:31:57 +0000, David Drysdale wrote:

> > This test uses the cloner binary to issue CIFS_IOC_COPYCHUNK_FILE
> > server-side copy requests.
> >
> > Signed-off-by: David Disseldorp <ddiss@suse.de>
> > ---
> >  tests/cifs/001     | 69 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >  tests/cifs/001.out | 21 +++++++++++++++++
> >  tests/cifs/group   |  6 +++++
> >  3 files changed, 96 insertions(+)
> >  create mode 100755 tests/cifs/001
> >  create mode 100644 tests/cifs/001.out
> >  create mode 100644 tests/cifs/group  
> 
> Does this also need a new tests/cifs/Makefile (so that e.g. the install
> target in tests/Makefile still works)?

Yes, you're right. Thanks for the feedback. I'll send through a new
version with the Makefile.

Cheers, David

  reply	other threads:[~2014-12-15 10:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-10  0:14 [PATCH 1/2] common: rename _require_btrfs_cloner to _require_cloner David Disseldorp
2014-12-10  0:14 ` [PATCH 2/2] cifs: add server-side copy sanity test David Disseldorp
2014-12-15  9:31   ` David Drysdale
2014-12-15 10:04     ` David Disseldorp [this message]
2014-12-15 10:43       ` [PATCH] cifs: add missing Makefile David Disseldorp
2014-12-10  3:38 ` [PATCH 1/2] common: rename _require_btrfs_cloner to _require_cloner Steve French

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=20141215110431.65c8bd80@plati.site \
    --to=ddiss@suse.de \
    --cc=drysdale@google.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-cifs@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 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.