From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jesse Barnes Subject: Re: CONFIG_NLS=m resulting in undefined reference to utf16s_to_utf8s causing build failure Date: Thu, 13 Jan 2011 07:55:56 -0800 Message-ID: <20110113075556.789ac3c3@jbarnes-vaio.home> References: <20110112203414.GA5657@fedora14-r610.oslab.blr.amer.dell.com> <20110112160229.7b8d82c1@jbarnes-desktop> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: Received: from cpoproxy1-pub.bluehost.com ([69.89.21.11]:33714 "HELO cpoproxy1-pub.bluehost.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1757190Ab1AMP4D (ORCPT ); Thu, 13 Jan 2011 10:56:03 -0500 In-Reply-To: Sender: linux-next-owner@vger.kernel.org List-ID: To: Len Brown Cc: Narendra_K@Dell.com, linux-kernel@vger.kernel.org, linux-next@vger.kernel.org, sfr@canb.auug.org.au, Matt_Domsch@Dell.com, Charles_Rose@Dell.com, Surya_Prabhakar@Dell.com On Wed, 12 Jan 2011 22:23:55 -0500 (EST) Len Brown wrote: > > So there's no other ACPI code that depends on this function? I'd hate > > to make PCI depend on NLS, so assuming ACPI doesn't need it (in which > > case the select or depend should be there), I guess it should be pulled > > into a common file that will always be included. > > No, nothing in the ACPI code uses utf16s_to_utf8s. > > I don't know anything about NLS, but it appears to be > something that file systems (befs, cifs, fat, hfs, isofs, jfs, etc) > use to to support native languages. > > BTW. I don't understand why pci-label.o appears twice above. > It used to be just the 2nd one, that depends on CONFIG_DMI. Ok, I'll drop this patch for now then since I haven't seen a fix yet and need to get Linus the rest of the changes. Thanks, Jesse