Use less confusing branch name for populating ksmbd changes in for-next

Use less confusing branch name for populating ksmbd changes in for-next

[Steve French]

Can we switch from using "cifsd-for-next" branch to "ksmbd-for-next"
when pulling changes
automatically into linux-next (since the module is fs/ksmbd/ksmbd.ko
using the branch name "ksmbd-for-next" is probably less confusing to
some)

ie from:
  https://github.com/smfrench/smb3-kernel/commits/cifsd-for-next
to
 https://github.com/smfrench/smb3-kernel/commits/ksmbd-for-next

-- 
Thanks,

Steve

Re: Use less confusing branch name for populating ksmbd changes in for-next

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 602 bytes --]

Hi Steve,

On Wed, 29 Sep 2021 13:22:34 -0500 Steve French <smfrench@gmail.com> wrote:
>
> Can we switch from using "cifsd-for-next" branch to "ksmbd-for-next"
> when pulling changes
> automatically into linux-next (since the module is fs/ksmbd/ksmbd.ko
> using the branch name "ksmbd-for-next" is probably less confusing to
> some)
> 
> ie from:
>   https://github.com/smfrench/smb3-kernel/commits/cifsd-for-next
> to
>  https://github.com/smfrench/smb3-kernel/commits/ksmbd-for-next

Done.  I also renamed the tree in linux-next from cifsd to ksmbd.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]