From: Greg KH <greg@kroah.com>
To: pefoley2@verizon.net
Cc: linux-kernel@vger.kernel.org, hjanssen@microsoft.com,
haiyangz@microsoft.com
Subject: Re: [PATCH resend] staging: hv: make HYPERV_UTILS depend on NLS to prevent a build error
Date: Tue, 3 May 2011 14:01:35 -0700 [thread overview]
Message-ID: <20110503210135.GA12954@kroah.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1105031642370.2706@gentoo.foleyremote.com>
On Tue, May 03, 2011 at 04:53:54PM -0400, pefoley2@verizon.net wrote:
> When HYPERV_UTILS=y and NLS=n the build fails with this error:
> MODPOST 3 modules ERROR: "utf8s_to_utf16s"
> [drivers/staging/hv/hv_utils.ko] undefined!
>
> This patch fixes this by adding a dependency on NLS to HYPERV_UTILS.
>
> Signed-off-by: Peter Foley <pefoley2@verizon.net>
> ---
> drivers/staging/hv/Kconfig | 2 +-
Nope, still not working, please fix your email client, it is messing up
the patch. Read the file, Documentation/email_client.txt for hints on
how to do this.
thanks,
greg k-h
prev parent reply other threads:[~2011-05-03 21:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-03 20:53 [PATCH resend] staging: hv: make HYPERV_UTILS depend on NLS to prevent a build error pefoley2
2011-05-03 21:01 ` Greg KH [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110503210135.GA12954@kroah.com \
--to=greg@kroah.com \
--cc=haiyangz@microsoft.com \
--cc=hjanssen@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pefoley2@verizon.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox