linux-cifs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve French <smfrench@gmail.com>
To: Pavel Shilovsky <piastryyy@gmail.com>
Cc: Ronnie Sahlberg <lsahlber@redhat.com>,
	linux-cifs <linux-cifs@vger.kernel.org>
Subject: Re: [PATCH 0/4] cifs: optimize opendir and save one roundtrip
Date: Wed, 15 Jan 2020 14:50:02 -0600	[thread overview]
Message-ID: <CAH2r5mv26iGyJjpye2_84hyDOBEN_Gv+bNvBGVP9tZ8B3W1rhg@mail.gmail.com> (raw)
In-Reply-To: <CAKywueRmjCYPGnZvVbM01Pc1kibKZQKit4mPfsE8ou+t=wOGXw@mail.gmail.com>

tentatively merged into cifs-2.6.git for-next (and added cc:stable for
the last patch in the series) pending more testing.

On Wed, Jan 8, 2020 at 6:34 PM Pavel Shilovsky <piastryyy@gmail.com> wrote:
>
> вт, 7 янв. 2020 г. в 19:08, Ronnie Sahlberg <lsahlber@redhat.com>:
>
> >
> > Pavel, Steve
> >
> > Please find an updated version of these patches.
> > It addresses Pavels concerns and adds an extra patch to set maxbufsize
> > correctly for two other functions that were found during review.
>
>
> Looks good overall, thanks!
>
> Reviewed-by: Pavel Shilovsky <pshilov@microsoft.com>
>
> Do we need a stable tag on the last patch?
>
> --
> Best regards,
> Pavel Shilovsky



-- 
Thanks,

Steve

      reply	other threads:[~2020-01-15 20:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-08  3:08 [PATCH 0/4] cifs: optimize opendir and save one roundtrip Ronnie Sahlberg
2020-01-08  3:08 ` [PATCH 1/4] cifs: prepare SMB2_query_directory to be used with compounding Ronnie Sahlberg
2020-01-08  3:08 ` [PATCH 2/4] cifs: create a helper function to parse the query-directory response buffer Ronnie Sahlberg
2020-01-08  3:08 ` [PATCH 3/4] cifs: use compounding for open and first query-dir for readdir() Ronnie Sahlberg
2020-01-08  3:08 ` [PATCH 4/4] cifs: set correct max-buffer-size for smb2_ioctl_init() Ronnie Sahlberg
2020-01-09  0:34 ` [PATCH 0/4] cifs: optimize opendir and save one roundtrip Pavel Shilovsky
2020-01-15 20:50   ` Steve French [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=CAH2r5mv26iGyJjpye2_84hyDOBEN_Gv+bNvBGVP9tZ8B3W1rhg@mail.gmail.com \
    --to=smfrench@gmail.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=lsahlber@redhat.com \
    --cc=piastryyy@gmail.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 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).