From: Peter Foley <pefoley2@verizon.net>
To: Greg KH <greg@kroah.com>
Cc: <linux-kernel@vger.kernel.org>, <hjanssen@microsoft.com>,
<haiyangz@microsoft.com>
Subject: Re: [PATCH] staging: hv: make HYPERV_UTILS depend on NLS to prevent a build error
Date: Tue, 3 May 2011 14:11:18 -0400 [thread overview]
Message-ID: <4DC04546.50901@verizon.net> (raw)
In-Reply-To: <20110503175703.GA19082@kroah.com>
On 5/3/2011 1:57 PM, Greg KH wrote:
> On Mon, Apr 25, 2011 at 07:52:18PM -0400, Peter Foley wrote:
>> This patch adds a dependency on NLS to HYPERV_UTILS to avoid a build error.
>>
>> Signed-off-by: Peter Foley <pefoley2@verizon.net>
>> ---
>> drivers/staging/hv/Kconfig | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/drivers/staging/hv/Kconfig b/drivers/staging/hv/Kconfig
>> index d41f380..76f0756 100644
>> --- a/drivers/staging/hv/Kconfig
>> +++ b/drivers/staging/hv/Kconfig
>> @@ -31,7 +31,7 @@ config HYPERV_NET
>> config HYPERV_UTILS
>> tristate "Microsoft Hyper-V Utilities driver"
>> - depends on CONNECTOR
>> + depends on CONNECTOR && NLS
>
> This patch doesn't apply at all, and I can't figure out why. Did your
> email client somehow mess it up?
>
> Care to resend it, with the proper information in the Changelog entry
> (i.e. what build error this is fixing) so I can apply it?
>
> thanks,
>
> greg k-h
Ok, I'll resend it.
I seem to have a problem with my email client corrupting patches.
I'm going to try a different one which will hopefully fix the problem.
Thanks,
Peter
prev parent reply other threads:[~2011-05-03 18:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-25 23:52 [PATCH] staging: hv: make HYPERV_UTILS depend on NLS to prevent a build error Peter Foley
2011-04-26 0:00 ` Greg KH
2011-04-26 0:53 ` Peter Foley
2011-05-03 17:33 ` Greg KH
2011-05-03 17:57 ` Greg KH
2011-05-03 18:11 ` Peter Foley [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=4DC04546.50901@verizon.net \
--to=pefoley2@verizon.net \
--cc=greg@kroah.com \
--cc=haiyangz@microsoft.com \
--cc=hjanssen@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
/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