linux-kernel - Re: linux-next: build failure after merge of the drivers-x86 tree

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: <4CAAFF99.6060504@canonical.com>
Date:	Tue, 05 Oct 2010 18:36:09 +0800
From:	Ike Panhc <ike.pan@...onical.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
CC:	Matthew Garrett <mjg59@...f.ucam.org>, linux-next@...r.kernel.org,
	linux-kernel@...r.kernel.org, Len Brown <len.brown@...el.com>
Subject: Re: linux-next: build failure after merge of the drivers-x86 tree

On 10/05/2010 12:11 PM, Stephen Rothwell wrote:
> Hi Matthew,
> 
> After merging the drivers-x86 tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> make[4]: *** No rule to make target `drivers/platform/x86/ideapad_laptop.c', needed by `drivers/platform/x86/ideapad_laptop.o'.  Stop.
> 
> Caused by commit 9efe5c1540a1e03cb2e0fca85e49fc4c57c6e771 ("ideapad:
> Change the driver name to ideapad-laptop").  The commit renames
> ideapad_acpi.c to ideapad-laptop.c but the Makefile uses ideapad_laptop.o
> (note underscore v. dash).
> 
> Presumably this was never even build tested :-(
> 
> I have used the drivers-x86 tree from next-20101004 for today.

Sorry, my fault.

This line is wrong,

+obj-$(CONFIG_IDEAPAD_LAPTOP)	+= ideapad_laptop.o

shall be

+obj-$(CONFIG_IDEAPAD_LAPTOP)	+= ideapad-laptop.o

How shall I fix it? resend the whole patches or just this one?

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