Merged into cifs-2.6.git for-next
On Sun, Jul 19, 2020 at 7:14 PM Randy Dunlap <rdunlap@xxxxxxxxxxxxx> wrote:
>
> Drop repeated words in multiple comments.
> (be, use, the, See)
>
> Signed-off-by: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
> Cc: Steve French <sfrench@xxxxxxxxx>
> Cc: linux-cifs@xxxxxxxxxxxxxxx
> Cc: samba-technical@xxxxxxxxxxxxxxx
> ---
> fs/cifs/cifsacl.h | 4 ++--
> fs/cifs/cifsglob.h | 2 +-
> fs/cifs/smb2pdu.h | 2 +-
> 3 files changed, 4 insertions(+), 4 deletions(-)
>
> --- linux-next-20200717.orig/fs/cifs/cifsacl.h
> +++ linux-next-20200717/fs/cifs/cifsacl.h
> @@ -132,7 +132,7 @@ struct cifs_ace {
> /*
> * The current SMB3 form of security descriptor is similar to what was used for
> * cifs (see above) but some fields are split, and fields in the struct below
> - * matches names of fields to the the spec, MS-DTYP (see sections 2.4.5 and
> + * matches names of fields to the spec, MS-DTYP (see sections 2.4.5 and
> * 2.4.6). Note that "CamelCase" fields are used in this struct in order to
> * match the MS-DTYP and MS-SMB2 specs which define the wire format.
> */
> @@ -178,7 +178,7 @@ struct smb3_acl {
>
> /*
> * Used to store the special 'NFS SIDs' used to persist the POSIX uid and gid
> - * See See http://technet.microsoft.com/en-us/library/hh509017(v=ws.10).aspx
> + * See http://technet.microsoft.com/en-us/library/hh509017(v=ws.10).aspx
> */
> struct owner_sid {
> u8 Revision;
> --- linux-next-20200717.orig/fs/cifs/cifsglob.h
> +++ linux-next-20200717/fs/cifs/cifsglob.h
> @@ -1466,7 +1466,7 @@ struct cifsInodeInfo {
> struct list_head llist; /* locks helb by this inode */
> /*
> * NOTE: Some code paths call down_read(lock_sem) twice, so
> - * we must always use use cifs_down_write() instead of down_write()
> + * we must always use cifs_down_write() instead of down_write()
> * for this semaphore to avoid deadlocks.
> */
> struct rw_semaphore lock_sem; /* protect the fields above */
> --- linux-next-20200717.orig/fs/cifs/smb2pdu.h
> +++ linux-next-20200717/fs/cifs/smb2pdu.h
> @@ -31,7 +31,7 @@
> * Note that, due to trying to use names similar to the protocol specifications,
> * there are many mixed case field names in the structures below. Although
> * this does not match typical Linux kernel style, it is necessary to be
> - * be able to match against the protocol specfication.
> + * able to match against the protocol specfication.
> *
> * SMB2 commands
> * Some commands have minimal (wct=0,bcc=0), or uninteresting, responses
--
Thanks,
Steve
