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]
Date:	Tue, 6 May 2008 02:17:52 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Andreas Mohr <andi@...as.de>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Mauro Carvalho Chehab <mchehab@...radead.org>
Subject: Re: Linux 2.6.26-rc1


* Stephen Rothwell <sfr@...b.auug.org.au> wrote:

> On Mon, 5 May 2008 09:30:31 +0200 Ingo Molnar <mingo@...e.hu> wrote:
> >
> > Subject: irda: PNP support for drivers/net/irda/nsc-ircc.c
> > From: Ingo Molnar <mingo@...e.hu>
> > Date: Sat May 03 21:21:13 CEST 2008
> > 
> > x86.git testing found the following build failure in latest -git:
> > 
> >  drivers/built-in.o: In function `nsc_ircc_pnp_probe':
> >  nsc-ircc.c:(.text+0xdf1b6): undefined reference to `pnp_get_resource'
> >  nsc-ircc.c:(.text+0xdf1d4): undefined reference to `pnp_get_resource'
> >  nsc-ircc.c:(.text+0xdf1ee): undefined reference to `pnp_get_resource'
> >  nsc-ircc.c:(.text+0xdf237): undefined reference to `pnp_get_resource'
> >  nsc-ircc.c:(.text+0xdf24c): undefined reference to `pnp_get_resource'
> >  drivers/built-in.o:nsc-ircc.c:(.text+0xdf266): more undefined references to `pnp_get_resource' follow
> >  make: *** [.tmp_vmlinux1] Error 1
> 
> This was discovered in linux-next and a patch posted on March 28 ...

hm, i do searches on lkml before posting patches but i cannot do 
searches on _every_ mailing list where patches might show up. There's 
just 30 hours in a day ;-)

perhaps linux-next should propagate all add-on fix patches it is 
carrying against subsystem trees if they are still relevant to -git, 
once the subsystem tree goes to -git, and re-post them to lkml in that 
case, to avoid duplicative work? Once it's on lkml i think most 
subsystem maintainers will find any missing patches.

> I (and I assume Andrew) have been carrying them since then but noone 
> took them up.  I guess (as Andrew pointed out to me) I should have 
> pushed them.

yeah.

	Ingo
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ