All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: kys@microsoft.com
Cc: linux-kernel@vger.kernel.org, devel@linuxdriverproject.org,
	olaf@aepfle.de, apw@canonical.com, vkuznets@redhat.com,
	jasowang@redhat.com, leann.ogasawara@canonical.com,
	Haiyang Zhang <haiyangz@microsoft.com>
Subject: Re: [PATCH 02/15] hyperv: Add a function to detect hv_device
Date: Thu, 1 Dec 2016 21:35:47 +0100	[thread overview]
Message-ID: <20161201203547.GB1602@kroah.com> (raw)
In-Reply-To: <1480613332-7788-2-git-send-email-kys@exchange.microsoft.com>

On Thu, Dec 01, 2016 at 09:28:39AM -0800, kys@exchange.microsoft.com wrote:
> From: Haiyang Zhang <haiyangz@microsoft.com>
> 
> Signed-off-by: Haiyang Zhang <haiyangz@microsoft.com>
> Signed-off-by: K. Y. Srinivasan <kys@microsoft.com>
> ---
>  drivers/hv/vmbus_drv.c |    6 ++++++
>  include/linux/hyperv.h |    2 ++
>  2 files changed, 8 insertions(+), 0 deletions(-)
> 
> diff --git a/drivers/hv/vmbus_drv.c b/drivers/hv/vmbus_drv.c
> index 0276d2e..1730ac0 100644
> --- a/drivers/hv/vmbus_drv.c
> +++ b/drivers/hv/vmbus_drv.c
> @@ -692,6 +692,12 @@ struct onmessage_work_context {
>  	struct hv_message msg;
>  };
>  
> +bool device_is_hyperv(struct device *dev)
> +{
> +	return dev->release == vmbus_device_release;
> +}
> +EXPORT_SYMBOL_GPL(device_is_hyperv);

Wait, eek, no!  That's NOT how you determine a device type, if you
really even ever need to do that.

Why are you needing this?  You should always "just know" what type of
device a struct device * is, that's what we rely on in the driver model.
Otherwise things get messy very very quickly.

Sorry, I can't take this without a ton of justification, and even then,
you need to do this correctly (and no, I'm not going to tell you how to
do that as I don't like it being done...)

greg k-h

  parent reply	other threads:[~2016-12-01 20:45 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-01 17:28 [PATCH 00/15] Drivers: hv: CPU management fixes and a new uio driver kys
2016-12-01 17:28 ` [PATCH 01/15] Drivers: hv: vmbus: Raise retry/wait limits in vmbus_post_msg() kys
2016-12-01 17:28   ` [PATCH 02/15] hyperv: Add a function to detect hv_device kys
2016-12-01 20:33     ` Greg KH
2016-12-02  5:46       ` KY Srinivasan
2016-12-01 20:35     ` Greg KH [this message]
2016-12-01 20:38       ` Greg KH
2016-12-02  6:02       ` KY Srinivasan
2016-12-02  6:48         ` Greg KH
2016-12-02  7:14           ` KY Srinivasan
2016-12-02  7:36             ` Greg KH
2016-12-02 15:38               ` KY Srinivasan
2016-12-02 16:02                 ` Greg KH
2016-12-02 21:41                   ` KY Srinivasan
2016-12-01 17:28   ` [PATCH 03/15] hyperv: Fix spelling of HV_UNKOWN kys
2016-12-01 17:28   ` [PATCH 04/15] Drivers: hv: vmbus: Prevent sending data on a rescinded channel kys
2016-12-01 20:36     ` Greg KH
2016-12-05 10:01     ` Dan Carpenter
2016-12-05 15:50       ` KY Srinivasan
2016-12-01 17:28   ` [PATCH 05/15] Drivers: hv: vmbus: Enhance the rescind callback functionality kys
2016-12-01 20:36     ` Greg KH
2016-12-01 17:28   ` [PATCH 06/15] hv: acquire vmbus_connection.channel_mutex in vmbus_free_channels() kys
2016-12-01 20:37     ` Greg KH
2016-12-02  6:11       ` KY Srinivasan
2016-12-01 17:28   ` [PATCH 07/15] hv: allocate synic pages for all present CPUs kys
2016-12-01 17:28   ` [PATCH 08/15] hv: init percpu_list in hv_synic_alloc() kys
2016-12-01 17:28   ` [PATCH 09/15] hv: change clockevents unbind tactics kys
2016-12-01 17:28   ` [PATCH 10/15] hv: switch to cpuhp state machine for synic init/cleanup kys
2016-12-01 17:28   ` [PATCH 11/15] hv: make CPU offlining prevention fine-grained kys
2016-12-01 17:28   ` [PATCH 12/15] hv: don't reset hv_context.tsc_page on crash kys
2016-12-01 17:28   ` [PATCH 13/15] vmbus: add support for dynamic device id's kys
2016-12-01 17:28   ` [PATCH 14/15] uio-hv-generic: new userspace i/o driver for VMBus kys
2016-12-01 17:28   ` [PATCH 15/15] Tools: hv: kvp: configurable external scripts path kys

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=20161201203547.GB1602@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=apw@canonical.com \
    --cc=devel@linuxdriverproject.org \
    --cc=haiyangz@microsoft.com \
    --cc=jasowang@redhat.com \
    --cc=kys@microsoft.com \
    --cc=leann.ogasawara@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olaf@aepfle.de \
    --cc=vkuznets@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.