On Thu, Jul 26, 2012 at 11:11:50AM +0800, wwang wrote:
> Hi Dan:
>
> Sorry to bother you.
> I can't find the maintainer of drivers/misc. So if I want to submit my
> driver as misc device, who should I contact to send my patch?
>From the MAINTAINERS file:
CHAR and MISC DRIVERS
M: Arnd Bergma
Hi Dan:
Sorry to bother you.
I can't find the maintainer of drivers/misc. So if I want to submit my
driver as misc device, who should I contact to send my patch?
Thank you very much. I really appreciate this help.
BR,
wwang
___
devel mailing list
devel
Hi Aaron:
Thank you. I will modify our host per your suggestion.
BR,
wwang
于 2012年07月25日 18:16, Aaron Lu 写道:
Hi Wei,
We do not use MMC_CAP_MAX_CURRENT_* anymore, for your host, I would
sugget you do something like this:
static void realtek_init(struct realtek_sdmmc *host)
{
struct mm
7:56:09
´ÓÏú#Ê۹ǸÉ×ßÏò¹Ü/Àí¸ßÊÖ¿ìËÙ ÍɱäÌØ/ѵ
Hanso_8608.xls
Description: Binary data
___
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
From: Haiyang Zhang
Date: Wed, 25 Jul 2012 11:08:42 -0700
> Reported-by: Jason Wang
> Signed-off-by: Haiyang Zhang
> Reviewed-by: K. Y. Srinivasan
Applied.
___
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/m
From: Haiyang Zhang
Date: Wed, 25 Jul 2012 11:08:41 -0700
> It prevents ring_size being set to a too small value.
>
> Reported-by: Jason Wang
> Signed-off-by: Haiyang Zhang
> Reviewed-by: K. Y. Srinivasan
Applied.
___
devel mailing list
devel@linux
Zimbra Account Warning
This mail is from Zimbra Administrator; we wish to bring to your notice the
Condition of your email account.
We have just noticed that you have exceeded your email Database limit of 500 MB
quota and your email IP is causing conflict because it is been accessed in
diff
Cc: Greg Kroah-Hartman
Cc: Larry Finger
Cc: Mike McCormack
Cc: wlanfae
Cc: Sean MacLennan
Cc: de...@driverdev.osuosl.org
Signed-off-by: Tim Gardner
---
.../staging/rtl8192e/rtl8192e/r8192E_firmware.c|9 +
.../staging/rtl8192e/rtl8192e/r8192E_firmware.h|4
drivers
Reported-by: Jason Wang
Signed-off-by: Haiyang Zhang
Reviewed-by: K. Y. Srinivasan
---
drivers/net/hyperv/rndis_filter.c | 11 ---
1 files changed, 4 insertions(+), 7 deletions(-)
diff --git a/drivers/net/hyperv/rndis_filter.c
b/drivers/net/hyperv/rndis_filter.c
index fbf5394..e5d61
It prevents ring_size being set to a too small value.
Reported-by: Jason Wang
Signed-off-by: Haiyang Zhang
Reviewed-by: K. Y. Srinivasan
---
drivers/net/hyperv/netvsc_drv.c |7 ++-
1 files changed, 6 insertions(+), 1 deletions(-)
diff --git a/drivers/net/hyperv/netvsc_drv.c b/drivers/
> -Original Message-
> From: Ben Hutchings [mailto:b...@decadent.org.uk]
> Sent: Wednesday, July 25, 2012 10:47 AM
> To: KY Srinivasan
> Cc: gre...@linuxfoundation.org; linux-ker...@vger.kernel.org;
> devel@linuxdriverproject.org; virtualizat...@lists.osdl.org; o...@aepfle.de;
> a...@cano
Ben,
At the outset I want to thank you for taking the time to review this code.
Given that Greg
has indicated that he will not be able to look at this patch set till 3.6 and
the nature of review
comments I have gotten from you and others, I will re-spin this patch set to
address all the
comment
On Wed, Jul 25, 2012 at 02:10:05PM +, KY Srinivasan wrote:
>
>
> > -Original Message-
> > From: Ben Hutchings [mailto:b...@decadent.org.uk]
> > Sent: Tuesday, July 24, 2012 9:11 PM
> > To: KY Srinivasan
> > Cc: gre...@linuxfoundation.org; linux-ker...@vger.kernel.org;
> > devel@linuxd
On 25/07/12 13:15, Martyn Welch wrote:
> On 25/07/12 10:20, Wolfgang Mauerer wrote:
>> On 24/07/12 23:53, Martyn Welch wrote:
>>> On 24/07/12 16:34, Wolfgang Mauerer wrote:
On 20/07/12 10:48, Martyn Welch wrote:
(...)
ca91c42x: Allow for exporting status information
>>>
>>> Don't ad
This is the patch I sent out yesterday for Linux to clean up the guest ID mess.
For FreeBSD, you can use the following constant:
HV_FREEBSD_VENDOR_ID0x8200
and use the function to generate the ID appropriately. Larry, I will forward
you the proposal for guest ID in a separate email.
> -Original Message-
> From: Ben Hutchings [mailto:b...@decadent.org.uk]
> Sent: Tuesday, July 24, 2012 9:14 PM
> To: KY Srinivasan
> Cc: gre...@linuxfoundation.org; linux-ker...@vger.kernel.org;
> devel@linuxdriverproject.org; virtualizat...@lists.osdl.org; o...@aepfle.de;
> a...@canonic
> -Original Message-
> From: Ben Hutchings [mailto:b...@decadent.org.uk]
> Sent: Tuesday, July 24, 2012 9:11 PM
> To: KY Srinivasan
> Cc: gre...@linuxfoundation.org; linux-ker...@vger.kernel.org;
> devel@linuxdriverproject.org; virtualizat...@lists.osdl.org; o...@aepfle.de;
> a...@canonic
Hi Devendra,
Thanks for cleaning up the driver. If I understand the code
correctly, the original author wanted to initialize wm_event once and
reuse it for multiple devices, and thus reference counted it with
ref_cnt.
For instance, each time gdm_usb_probe() is called, it may call
register_wimax_
> -Original Message-
> From: Olaf Hering [mailto:o...@aepfle.de]
> Sent: Wednesday, July 25, 2012 4:17 AM
> To: KY Srinivasan
> Cc: gre...@linuxfoundation.org; linux-ker...@vger.kernel.org;
> devel@linuxdriverproject.org; a...@canonical.com
> Subject: Re: [PATCH 1/1] Drivers: hv: Cleanup
On 25/07/12 10:20, Wolfgang Mauerer wrote:
> On 24/07/12 23:53, Martyn Welch wrote:
>> On 24/07/12 16:34, Wolfgang Mauerer wrote:
>>> On 20/07/12 10:48, Martyn Welch wrote:
On 19/07/12 23:39, Greg Kroah-Hartman wrote:
> On Thu, Jul 19, 2012 at 08:08:50PM +0100, Martyn Welch wrote:
>>>
Hi Wei,
We do not use MMC_CAP_MAX_CURRENT_* anymore, for your host, I would
sugget you do something like this:
static void realtek_init(struct realtek_sdmmc *host)
{
struct mmc_host *mmc = host->mmc;
... ...
/*
* since you have set MMC_CAP_MAX_CURRENT_800 in your
On 24/07/12 23:53, Martyn Welch wrote:
> On 24/07/12 16:34, Wolfgang Mauerer wrote:
>> On 20/07/12 10:48, Martyn Welch wrote:
>>> On 19/07/12 23:39, Greg Kroah-Hartman wrote:
On Thu, Jul 19, 2012 at 08:08:50PM +0100, Martyn Welch wrote:
>>
>>> Still in two minds about whether we should keep vm
On Tue, Jul 24, K. Y. Srinivasan wrote:
> +/*
> + * The guest OS needs to register the guest ID with the hypervisor.
> + * The guest ID is a 64 bit entity and the structure of this ID is
> + * specified in the Hyper-V specification:
> + *
> + * http://msdn.microsoft.com/en-us/library/windows/
> +
On Wed, Jul 25, 2012 at 10:28:39AM +0800, wwang wrote:
> 于 2012年07月24日 22:07, Borislav Petkov 写道:
> >Kernel is Linus' from yesterday: v3.5-709-ga6be1fcbc57f and config
> >is attached.
>
> The compilation process is still OK with your config.
Yes, but not with the kernel I'm using. If you'd tried
On Tue, Jul 24, K. Y. Srinivasan wrote:
> +++ b/drivers/hv/hv_kvp.c
> @@ -48,13 +48,24 @@ static struct {
> void *kvp_context; /* for the channel callback */
> } kvp_transaction;
>
> +/*
> + * Before we can accept KVP messages from the host, we need
> + * to handshake with the user level
25 matches
Mail list logo
