netdev - Re: drivers/net/cris/eth_v10.c:1715:2: error: too many arguments to function 'e100rxtx

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]

Message-ID: <20121006010744.GA7525@localhost>
Date:	Sat, 6 Oct 2012 09:07:44 +0800
From:	Fengguang Wu <fengguang.wu@...el.com>
To:	Jesper Nilsson <jesper.nilsson@...s.com>
Cc:	David Miller <davem@...emloft.net>,
	"kernel-janitors@...r.kernel.org" <kernel-janitors@...r.kernel.org>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: drivers/net/cris/eth_v10.c:1715:2: error: too many arguments to
 function 'e100rxtx_interrupt'

On Fri, Oct 05, 2012 at 11:24:22PM +0200, Jesper Nilsson wrote:
> On Wed, Oct 03, 2012 at 10:26:57PM +0200, Jesper Nilsson wrote:
> > On Wed, Oct 03, 2012 at 08:40:40PM +0200, David Miller wrote:
> > > From: Jesper Nilsson <jesper.nilsson@...s.com>
> > > Date: Wed, 3 Oct 2012 12:46:52 +0200
> > > 
> > > > On Fri, Sep 28, 2012 at 03:06:08PM +0200, Fengguang Wu wrote:
> > > >> Hi Jesper,
> > > > 
> > > > Hi!
> > > > 
> > > >> FYI, a rather old build bug that's introduced by
> > > >> 
> > > >> bafef0a cris build fixes: update eth_v10.c ethernet driver
> > > >> 
> > > >> All error/warnings:
> > > >> 
> > > >> drivers/net/cris/eth_v10.c: In function 'e100_netpoll':
> > > >> drivers/net/cris/eth_v10.c:1715:2: error: too many arguments to function 'e100rxtx_interrupt'
> > > >> drivers/net/cris/eth_v10.c:1131:1: note: declared here
> > > > 
> > > > Yep, I can't figure out why the followup patches never reached mainline,
> > > > but we have fixes for exactly that in our in-house tree.
> > > > I'll push some move patches after this merge window.
> > > 
> > > It's a bug fix, even worse a build fix, why want until after the merge
> > > window?
> > 
> > Aye, true, I'll just have to make sure I don't get any other change from
> > the inhouse tree.
> 
> Turns out this was already fixed in mainline since August.

Embarrassing.. It must be testing some git tree that's based on one
upstream HEAD sometime between where the bug was introduced and where
it's fixed.

Thanks,
Fengguang
--
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