Re: [PATCH 1/1] drivers:hv:vmbus Allow for more than one MMIO range for children.

From: Greg KH
Date: Tue Jan 20 2015 - 16:04:08 EST

Next message: Nadav Amit: "Re: [v3 13/26] KVM: Define a new interface kvm_find_dest_vcpu() for VT-d PI"
Previous message: Stephen Smalley: "Re: [PATCH] Selinux/hooks.c: Fix a NULL pointer dereference caused by semop()"
In reply to: Jake Oshins: "[PATCH 1/1] drivers:hv:vmbus Allow for more than one MMIO range for children."
Next in thread: KY Srinivasan: "RE: [PATCH 1/1] drivers:hv:vmbus Allow for more than one MMIO range for children."
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Tue, Jan 20, 2015 at 01:59:40PM -0800, Jake Oshins wrote:
> Signed-off-by: Jake Oshins <jakeo@xxxxxxxxxxxxx>

No changelog body explaining why this is needed and what it fixes?

Please redo.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Next message: Nadav Amit: "Re: [v3 13/26] KVM: Define a new interface kvm_find_dest_vcpu() for VT-d PI"
Previous message: Stephen Smalley: "Re: [PATCH] Selinux/hooks.c: Fix a NULL pointer dereference caused by semop()"
In reply to: Jake Oshins: "[PATCH 1/1] drivers:hv:vmbus Allow for more than one MMIO range for children."
Next in thread: KY Srinivasan: "RE: [PATCH 1/1] drivers:hv:vmbus Allow for more than one MMIO range for children."
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]