linux-kernel - Re: [PATCH] phy: Add missing forward declaration (fixes compiler warning)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sun, 15 Aug 2010 00:01:48 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	weil@...l.berlios.de
Cc:	linux-kernel@...r.kernel.org, avorontsov@...mvista.com,
	ben@...adent.org.uk, jgunthorpe@...idianresearch.com
Subject: Re: [PATCH] phy: Add missing forward declaration (fixes compiler
 warning)

From: Stefan Weil <weil@...l.berlios.de>
Date: Tue,  3 Aug 2010 19:04:01 +0200

> Without forward declaration for struct sk_buff, compilation
> of drivers/net/phy/fixed.c results in a warning:

linux/phy.h has had the appropriate forward declaration since
July 16th

In fact the forward declaration was added by the only patch
that added references to sk_buff in that header file:

--------------------
commit c1f19b51d1d87f3e3bb7e6648f43f7d57ed2da6b
Author: Richard Cochran <richardcochran@...il.com>
Date:   Sat Jul 17 08:49:36 2010 +0000

    net: support time stamping in phy devices.
    
 ...
--------------------

As per your warning:

--------------------
  CC      drivers/net/phy/fixed.o
In file included from drivers/net/phy/fixed.c:20:
include/linux/phy.h:342: warning: 'struct sk_buff' declared inside parameter list
include/linux/phy.h:342: warning: its scope is only this definition or declaration, which is probably not what you want
include/linux/phy.h:343: warning: 'struct sk_buff' declared inside parameter list

(tested with linux kernel for openwrt / ar7, gcc-4.1.2)
--------------------

Line 342 in the current tree lands on a comment.  Please don't
post patches against external trees, or you'll always run into
problems like this.  Who knows what patches happen to be applied
to the openwrt tree you happen to have.

Always spin and test patches against upstream.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/