netdev - Re: blackfin drivers/net/smc91x.c build error

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080610135349.GA30792@cs181133002.pp.htv.fi>
Date:	Tue, 10 Jun 2008 16:53:49 +0300
From:	Adrian Bunk <bunk@...nel.org>
To:	Mike Frysinger <vapier.adi@...il.com>
Cc:	Bryan Wu <cooloney@...nel.org>, Jeff Garzik <jeff@...zik.org>,
	netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: blackfin drivers/net/smc91x.c build error

On Fri, Jun 06, 2008 at 03:52:09PM -0400, Mike Frysinger wrote:
> On Fri, Jun 6, 2008 at 12:22 PM, Adrian Bunk <bunk@...nel.org> wrote:
> > drivers/net/smc91x.c fails as follows on blackfin:
> > ...
> >  CC      drivers/net/smc91x.o
> > ...
> > /home/bunk/linux/kernel-2.6/git/linux-2.6/drivers/net/smc91x.c:1863:36: error: macro "SMC_GET_MAC_ADDR" passed 2 arguments, but takes just 1
> > ...
> 
> it's a known issue (been known for quite a long time actually).  Bryan
> has brought this up in the past already.

Is my suggestion of reverting commit 099c736a470c8080a166e7a089f1e48e15f9947c
correct or how else should it be resolved?

This issue is the only remaining problem preventing that all blackfin 
defconfigs will compile in 2.6.26...

> -mike

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html