Le 10/02/2012 22:41, Mike Frysinger a écrit :
On Friday 10 February 2012 15:57:50 Albert ARIBAUD wrote:
Le 10/02/2012 21:32, Mike Frysinger a écrit :
On Friday 10 February 2012 14:39:12 Albert ARIBAUD wrote:
Le 07/02/2012 16:20, Mike Frysinger a écrit :
On Monday 06 February 2012 16:01:56
Le 07/02/2012 16:20, Mike Frysinger a écrit :
On Monday 06 February 2012 16:01:56 Albert ARIBAUD wrote:
Le 06/02/2012 21:57, Mike Frysinger a écrit :
The would give me compiler warnings for unused variables. How does that
help?
does gcc issue warnings ? doesn't seem to do so for me.
Some
On Friday 10 February 2012 14:39:12 Albert ARIBAUD wrote:
Le 07/02/2012 16:20, Mike Frysinger a écrit :
On Monday 06 February 2012 16:01:56 Albert ARIBAUD wrote:
Le 06/02/2012 21:57, Mike Frysinger a écrit :
Is there a keep attribute like the linker has for sections?
yes,
Le 10/02/2012 21:32, Mike Frysinger a écrit :
On Friday 10 February 2012 14:39:12 Albert ARIBAUD wrote:
Le 07/02/2012 16:20, Mike Frysinger a écrit :
On Monday 06 February 2012 16:01:56 Albert ARIBAUD wrote:
Le 06/02/2012 21:57, Mike Frysinger a écrit :
Is there a keep attribute like the
On Friday 10 February 2012 15:57:50 Albert ARIBAUD wrote:
Le 10/02/2012 21:32, Mike Frysinger a écrit :
On Friday 10 February 2012 14:39:12 Albert ARIBAUD wrote:
Le 07/02/2012 16:20, Mike Frysinger a écrit :
On Monday 06 February 2012 16:01:56 Albert ARIBAUD wrote:
Le 06/02/2012 21:57,
On Monday 06 February 2012 16:01:56 Albert ARIBAUD wrote:
Le 06/02/2012 21:57, Mike Frysinger a écrit :
The would give me compiler warnings for unused variables. How does that
help?
does gcc issue warnings ? doesn't seem to do so for me.
Some do, and some will.
vague ... be nice to
On Monday 06 February 2012 16:44:36 Troy Kisky wrote:
On 2/6/2012 1:57 PM, Mike Frysinger wrote:
On Monday 06 February 2012 15:17:32 Troy Kisky wrote:
On 2/6/2012 12:07 PM, Mike Frysinger wrote:
On Monday 06 February 2012 13:48:13 Troy Kisky wrote:
On 2/4/2012 8:38 PM, Mike Frysinger
On 2/4/2012 8:38 PM, Mike Frysinger wrote:
On Saturday 04 February 2012 22:02:46 Troy Kisky wrote:
--- a/drivers/net/phy/broadcom.c
+++ b/drivers/net/phy/broadcom.c
-static struct phy_driver BCM5461S_driver = {
+struct phy_driver BCM5461S_driver __phy_entry = {
why do you have to remove the
On Monday 06 February 2012 13:48:13 Troy Kisky wrote:
On 2/4/2012 8:38 PM, Mike Frysinger wrote:
On Saturday 04 February 2012 22:02:46 Troy Kisky wrote:
--- a/drivers/net/phy/broadcom.c
+++ b/drivers/net/phy/broadcom.c
-static struct phy_driver BCM5461S_driver = {
+struct phy_driver
On 2/6/2012 12:07 PM, Mike Frysinger wrote:
On Monday 06 February 2012 13:48:13 Troy Kisky wrote:
On 2/4/2012 8:38 PM, Mike Frysinger wrote:
On Saturday 04 February 2012 22:02:46 Troy Kisky wrote:
--- a/drivers/net/phy/broadcom.c
+++ b/drivers/net/phy/broadcom.c
-static struct phy_driver
Le 05/02/2012 21:40, Mike Frysinger a écrit :
On Sunday 05 February 2012 08:26:57 Albert ARIBAUD wrote:
Le 05/02/2012 04:38, Mike Frysinger a écrit :
On Saturday 04 February 2012 22:02:46 Troy Kisky wrote:
--- a/include/phy.h
+++ b/include/phy.h
+extern struct phy_driver __phy_entry_start,
Le 06/02/2012 21:17, Troy Kisky a écrit :
On 2/6/2012 12:07 PM, Mike Frysinger wrote:
On Monday 06 February 2012 13:48:13 Troy Kisky wrote:
On 2/4/2012 8:38 PM, Mike Frysinger wrote:
On Saturday 04 February 2012 22:02:46 Troy Kisky wrote:
--- a/drivers/net/phy/broadcom.c
+++
On Monday 06 February 2012 15:17:32 Troy Kisky wrote:
On 2/6/2012 12:07 PM, Mike Frysinger wrote:
On Monday 06 February 2012 13:48:13 Troy Kisky wrote:
On 2/4/2012 8:38 PM, Mike Frysinger wrote:
On Saturday 04 February 2012 22:02:46 Troy Kisky wrote:
--- a/drivers/net/phy/broadcom.c
+++
Le 06/02/2012 21:57, Mike Frysinger a écrit :
The would give me compiler warnings for unused variables. How does that
help?
does gcc issue warnings ? doesn't seem to do so for me.
Some do, and some will.
Is there a keep attribute like the linker has for sections?
yes,
On 2/6/2012 1:57 PM, Mike Frysinger wrote:
On Monday 06 February 2012 15:17:32 Troy Kisky wrote:
On 2/6/2012 12:07 PM, Mike Frysinger wrote:
On Monday 06 February 2012 13:48:13 Troy Kisky wrote:
On 2/4/2012 8:38 PM, Mike Frysinger wrote:
On Saturday 04 February 2012 22:02:46 Troy Kisky
Hi Mike,
Le 05/02/2012 04:38, Mike Frysinger a écrit :
On Saturday 04 February 2012 22:02:46 Troy Kisky wrote:
--- a/drivers/net/phy/broadcom.c
+++ b/drivers/net/phy/broadcom.c
-static struct phy_driver BCM5461S_driver = {
+struct phy_driver BCM5461S_driver __phy_entry = {
why do you have
On Sunday 05 February 2012 08:26:57 Albert ARIBAUD wrote:
Le 05/02/2012 04:38, Mike Frysinger a écrit :
On Saturday 04 February 2012 22:02:46 Troy Kisky wrote:
--- a/include/phy.h
+++ b/include/phy.h
+extern struct phy_driver __phy_entry_start, __phy_entry_end;
linker symbols
On Saturday 04 February 2012 22:02:46 Troy Kisky wrote:
--- a/drivers/net/phy/broadcom.c
+++ b/drivers/net/phy/broadcom.c
-static struct phy_driver BCM5461S_driver = {
+struct phy_driver BCM5461S_driver __phy_entry = {
why do you have to remove the static ? that shouldn't affect the
On 05.02.2012 04:38, Mike Frysinger wrote:
On Saturday 04 February 2012 22:02:46 Troy Kisky wrote:
--- a/drivers/net/phy/broadcom.c
+++ b/drivers/net/phy/broadcom.c
-static struct phy_driver BCM5461S_driver = {
+struct phy_driver BCM5461S_driver __phy_entry = {
why do you have to remove the
19 matches
Mail list logo