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:	Wed, 5 May 2010 10:39:58 +0200
From:	Tobias Klauser <tklauser@...tanz.ch>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Greg KH <greg@...ah.com>, linux-next@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: linux-next: build failure after merge of the staging tree

Hi Stephen,

On 2010-05-05 at 04:37:54 +0200, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> On Mon, 3 May 2010 18:17:21 +0200 Tobias Klauser <tklauser@...tanz.ch> wrote:
> >
> > I just built the current linux-next (20100503) with the patches applied
> > (including Greg's Kconfig change) on x86_64 with allmodconfig and wasn't
> > able to reproduce the build failure.
> > 
> > Any pointers on how to reproduce and/or fix this would be appreciated.
> 
> Of course, if you force this driver to be built in (as Greg's Kconfig
> change presumably did), then you won't get these errors.
> 
> The real solution is that SERIAL_ALTERA_JTAGUART_CONSOLE needs to depend
> on SERIAL_ALTERA_JTAGUART=y (instead of just SERIAL_ALTERA_JTAGUART) and
> similarly for the other.

Thanks for your help! I resubmitted an updated version of the patches
([1], [2]) including the changes pointed out above (compile tested
against linux-next as of 20100505 with allmodconfig on x86_64).

[1] Message-Id:
095aab012b2a6b3bbf4c7bc04294bb9c19316318.1273048151.git.tklauser@...tanz.ch
[2] Message-Id:
e83e74abd82079284d5c8f62b78f2417ebc9ee27.1273048151.git.tklauser@...tanz.ch

Cheers,
Tobias
--
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