Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: Ronnie Sahlberg <lsahlber-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: linux-cifs <linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Cc: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: [PATCH 0/2] cifs: Add attribute read/write support to SMB2+
Date: Thu, 24 Aug 2017 11:24:54 +1000	[thread overview]
Message-ID: <20170824012456.10977-1-lsahlber@redhat.com> (raw)

Tested against both Samba shares as well as Win7 shares.

Version 5:
* Learn how to use endianness macros correctly.

Version 4:
* Remove remaining CamelCase
* ea_value_length is __le16, not __u16

Version 3:
* No CamelCase in new code.
* No declarations inside loops.

Version 2:
* For reading attributes we need FILE_READ_EA not FILE_READ_ATTRIBUTES

             reply	other threads:[~2017-08-24  1:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-24  1:24 Ronnie Sahlberg [this message]
     [not found] ` <20170824012456.10977-1-lsahlber-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-08-24  1:24   ` [PATCH 1/2] cifs: Add support for reading attributes on SMB2+ Ronnie Sahlberg
     [not found]     ` <20170824012456.10977-2-lsahlber-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-08-29 22:15       ` Pavel Shilovskiy
2017-08-24  1:24   ` [PATCH 2/2] cifs: Add support for writing " Ronnie Sahlberg
     [not found]     ` <20170824012456.10977-3-lsahlber-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-08-29 22:16       ` Pavel Shilovskiy
2017-08-27 22:02   ` [PATCH 0/2] cifs: Add attribute read/write support to SMB2+ Steve French
  -- strict thread matches above, loose matches on Subject: below --
2017-08-23 22:51 Ronnie Sahlberg
2017-08-21 22:23 Ronnie Sahlberg
2017-08-18  5:07 Ronnie Sahlberg

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=20170824012456.10977-1-lsahlber@redhat.com \
    --to=lsahlber-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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