On Mon, Aug 12, 2019 at 10:19:27AM -0700, Kees Cook wrote:
> On Wed, Aug 07, 2019 at 01:50:42PM +0300, Dan Carpenter wrote:
> > On Tue, Aug 06, 2019 at 06:41:44PM +0200, Oliver Hartkopp wrote:
> > > I compiled the code (the original version), but I do not get that "Should
> > > it
> > > be
On Wed, Aug 07, 2019 at 01:50:42PM +0300, Dan Carpenter wrote:
> On Tue, Aug 06, 2019 at 06:41:44PM +0200, Oliver Hartkopp wrote:
> > I compiled the code (the original version), but I do not get that "Should it
> > be static?" warning:
> >
> > user@box:~/net-next$ make C=1
> > CALL
On 12/08/2019 07.48, maowenan wrote:
On 2019/8/7 0:41, Oliver Hartkopp wrote:
I compiled the code (the original version), but I do not get that "Should it be
static?" warning:
here are my steps for net/can/bcm.c,
make allmodconfig ARCH=mips CROSS_COMPILE=mips-linux-gnu-
make C=2
On 2019/8/7 0:41, Oliver Hartkopp wrote:
> Hello Dan,
>
> On 06/08/2019 15.52, Dan Carpenter wrote:
>> On Fri, Aug 02, 2019 at 10:10:20AM +0200, Oliver Hartkopp wrote:
>
>>> Btw. what kind of compiler/make switches are you using so that I can see
>>> these warnings myself the next time?
>>
>>
On Tue, Aug 06, 2019 at 06:41:44PM +0200, Oliver Hartkopp wrote:
> I compiled the code (the original version), but I do not get that "Should it
> be static?" warning:
>
> user@box:~/net-next$ make C=1
> CALLscripts/checksyscalls.sh
> CALLscripts/atomic/check-atomics.sh
> DESCEND
Hello Dan,
On 06/08/2019 15.52, Dan Carpenter wrote:
On Fri, Aug 02, 2019 at 10:10:20AM +0200, Oliver Hartkopp wrote:
Btw. what kind of compiler/make switches are you using so that I can see
these warnings myself the next time?
These are Sparse warnings, not from GCC.
I compiled the code
On Fri, Aug 02, 2019 at 10:10:20AM +0200, Oliver Hartkopp wrote:
> On 02/08/2019 05.36, Mao Wenan wrote:
> > There are two warings in net/can, fix them by setting bcm_sock_no_ioctlcmd
> > and raw_sock_no_ioctlcmd as static.
> >
> > net/can/bcm.c:1683:5: warning: symbol 'bcm_sock_no_ioctlcmd' was
please drop this mail.
On 2019/8/5 9:22, Mao Wenan wrote:
> There are two warnings in net/can, fix them by setting bcm_sock_no_ioctlcmd
> and raw_sock_no_ioctlcmd as static.
>
> net/can/bcm.c:1683:5: warning: symbol 'bcm_sock_no_ioctlcmd' was not
> declared. Should it be static?
>
There are two warnings in net/can, fix them by setting bcm_sock_no_ioctlcmd
and raw_sock_no_ioctlcmd as static.
net/can/bcm.c:1683:5: warning: symbol 'bcm_sock_no_ioctlcmd' was not declared.
Should it be static?
net/can/raw.c:840:5: warning: symbol 'raw_sock_no_ioctlcmd' was not declared.
On 2019/8/2 16:59, Sergei Shtylyov wrote:
> Hello!
>
> On 02.08.2019 6:36, Mao Wenan wrote:
>
>> There are two warings in net/can, fix them by setting bcm_sock_no_ioctlcmd
>
>Warnings. :-)
Thanks, I will send v2.
>
>> and raw_sock_no_ioctlcmd as static.
>>
>> net/can/bcm.c:1683:5:
Hello!
On 02.08.2019 6:36, Mao Wenan wrote:
There are two warings in net/can, fix them by setting bcm_sock_no_ioctlcmd
Warnings. :-)
and raw_sock_no_ioctlcmd as static.
net/can/bcm.c:1683:5: warning: symbol 'bcm_sock_no_ioctlcmd' was not declared.
Should it be static?
On 2019/8/2 16:10, Oliver Hartkopp wrote:
> On 02/08/2019 05.36, Mao Wenan wrote:
>> There are two warings in net/can, fix them by setting bcm_sock_no_ioctlcmd
>> and raw_sock_no_ioctlcmd as static.
>>
>> net/can/bcm.c:1683:5: warning: symbol 'bcm_sock_no_ioctlcmd' was not
>> declared. Should
On 02/08/2019 05.36, Mao Wenan wrote:
There are two warings in net/can, fix them by setting bcm_sock_no_ioctlcmd
and raw_sock_no_ioctlcmd as static.
net/can/bcm.c:1683:5: warning: symbol 'bcm_sock_no_ioctlcmd' was not declared.
Should it be static?
net/can/raw.c:840:5: warning: symbol
There are two warings in net/can, fix them by setting bcm_sock_no_ioctlcmd
and raw_sock_no_ioctlcmd as static.
net/can/bcm.c:1683:5: warning: symbol 'bcm_sock_no_ioctlcmd' was not declared.
Should it be static?
net/can/raw.c:840:5: warning: symbol 'raw_sock_no_ioctlcmd' was not declared.
Should
14 matches
Mail list logo
