[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAH2r5mv43iPuAgvM699A5TstZGzHj=WOsYd8ffmk1DSUsQXdrA@mail.gmail.com>
Date: Tue, 5 Nov 2019 17:00:03 -0600
From: Steve French <smfrench@...il.com>
To: kbuild test robot <lkp@...el.com>
Cc: Aurelien Aptel <aaptel@...e.com>, kbuild-all@...ts.01.org,
CIFS <linux-cifs@...r.kernel.org>,
samba-technical <samba-technical@...ts.samba.org>,
Steve French <stfrench@...rosoft.com>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH cifs] cifs: smb3_crypto_shash_allocate can be static
FYI - I updated cifs-2.6.for-next with the equivalent change (fixing a
line change to one of Aurelien's patches in the multichannel series)
On Mon, Nov 4, 2019 at 1:59 AM kbuild test robot <lkp@...el.com> wrote:
>
>
> Fixes: 4d1cc0309f7e ("cifs: try opening channels after mounting")
> Signed-off-by: kbuild test robot <lkp@...el.com>
> ---
> smb2transport.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/cifs/smb2transport.c b/fs/cifs/smb2transport.c
> index 1af789871ec2e..86501239cef55 100644
> --- a/fs/cifs/smb2transport.c
> +++ b/fs/cifs/smb2transport.c
> @@ -48,7 +48,7 @@ smb2_crypto_shash_allocate(struct TCP_Server_Info *server)
> &server->secmech.sdeschmacsha256);
> }
>
> -int
> +static int
> smb3_crypto_shash_allocate(struct TCP_Server_Info *server)
> {
> struct cifs_secmech *p = &server->secmech;
--
Thanks,
Steve
Powered by blists - more mailing lists