From: Pavel Shilovsky <piastryyy@gmail.com>
To: Jeff Layton <jlayton@samba.org>
Cc: linux-cifs@vger.kernel.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: SMB2 protocol support for CIFS Linux kernel module
Date: Thu, 20 Oct 2011 19:27:06 +0400 [thread overview]
Message-ID: <CAKywueSJoApMc8RrDO-nfd64FWdNG_Zdw2-Mse01wK3B0h+VzA@mail.gmail.com> (raw)
In-Reply-To: <20111020112058.185cae5e@barsoom.rdu.redhat.com>
2011/10/20 Jeff Layton <jlayton@samba.org>:
> On Fri, 14 Oct 2011 13:31:10 +0400
> Pavel Shilovsky <piastryyy@gmail.com> wrote:
>
>> Hi all!
>>
>> I rebased my cifs-3.2-current branch on top of current
>> cifs-2.6/master. It includes all patches (lock caching + smb2 patches)
>> I want to get into 3.2 release.
>>
>> http://git.altlinux.org/people/piastry/public/?p=cifs-2.6.git;a=shortlog;h=refs/heads/cifs-3.2-current
>>
>> Comments are welcome!
>>
>> --
>> Best regards,
>> Pavel Shilovsky.
>
> I started looking over them, but it's hard to comment since almost all
> of them haven't been sent to the list and there's nothing to reply to.
>
> Would it be possible to send this to the list in one or more patchsets
> so it can be reviewed like any other series?
>
> Thanks,
> --
> Jeff Layton <jlayton@samba.org>
>
Thanks! I will split it into several patchset and post to the list in
this case. The last version of patches is here:
http://git.altlinux.org/people/piastry/public/?p=cifs-2.6.git;a=shortlog;h=refs/heads/cifs-3.2-aread
--
Best regards,
Pavel Shilovsky.
next prev parent reply other threads:[~2011-10-20 15:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-14 9:31 SMB2 protocol support for CIFS Linux kernel module Pavel Shilovsky
2011-10-20 15:20 ` Jeff Layton
2011-10-20 15:27 ` Pavel Shilovsky [this message]
[not found] ` <CAKywueSJoApMc8RrDO-nfd64FWdNG_Zdw2-Mse01wK3B0h+VzA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-10-25 6:16 ` Pavel Shilovsky
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=CAKywueSJoApMc8RrDO-nfd64FWdNG_Zdw2-Mse01wK3B0h+VzA@mail.gmail.com \
--to=piastryyy@gmail.com \
--cc=jlayton@samba.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@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).