All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Ky Srinivasan <ksrinivasan@novell.com>
Cc: hpa@zytor.com, hjanssen@microsoft.com, mingo@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Hyperv: Export the symbol that tracks hyperv features and recommendations
Date: Mon, 21 Jun 2010 14:13:19 -0700	[thread overview]
Message-ID: <20100621211319.GA25447@kroah.com> (raw)
In-Reply-To: <4C1F80160200003000087BA8@sinclair.provo.novell.com>

On Mon, Jun 21, 2010 at 03:07:02PM -0600, Ky Srinivasan wrote:
> 
>  
> From: K. Y. Srinivasan <ksrinivasan@novell.com>
> Subject:  Export the symbol  for hyperv drivers to access hyperv
> features and recommendations. This patch is needed by the hyperV clocksource driver.
> 
> Signed-off-by: K. Y. Srinivasan <ksrinivasan@novell.com>
> 
> Index: linux.trees.git/arch/x86/kernel/cpu/mshyperv.c
> ===================================================================
> --- linux.trees.git.orig/arch/x86/kernel/cpu/mshyperv.c	2010-05-18 10:14:02.000000000 -0600
> +++ linux.trees.git/arch/x86/kernel/cpu/mshyperv.c	2010-05-18 14:12:11.000000000 -0600
> @@ -18,6 +18,7 @@
>  #include <asm/mshyperv.h>
>  
>  struct ms_hyperv_info ms_hyperv;
> +EXPORT_SYMBOL(ms_hyperv);

EXPORT_SYMBOL_GPL()?  Didn't you have it that way in your previous
patch?

thanks,

greg k-h

  reply	other threads:[~2010-06-21 21:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-21 21:07 [PATCH] Hyperv: Export the symbol that tracks hyperv features and recommendations Ky Srinivasan
2010-06-21 21:13 ` Greg KH [this message]
2010-06-22 14:36   ` Ky Srinivasan
  -- strict thread matches above, loose matches on Subject: below --
2010-05-07 22:43 RFC - Cleaned up hypervisor layer H. Peter Anvin
2010-05-08  1:58 ` [tip:x86/cpu] x86: Clean up the " tip-bot for H. Peter Anvin
2010-05-19 16:54   ` [PATCH] Hyperv: Export the symbol that tracks hyperv features and recommendations Ky Srinivasan
2010-05-19 17:03     ` Greg KH

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=20100621211319.GA25447@kroah.com \
    --to=greg@kroah.com \
    --cc=hjanssen@microsoft.com \
    --cc=hpa@zytor.com \
    --cc=ksrinivasan@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.