usb_alphatrack_delete() frees "dev" so we can't use it on that path.
Signed-off-by: Dan Carpenter
diff --git a/drivers/staging/frontier/alphatrack.c
b/drivers/staging/frontier/alphatrack.c
index 5590ebf..817f837 100644
--- a/drivers/staging/frontier/alphatrack.c
+++ b/drivers/staging/frontier/a
On Mon, 2013-07-22 at 15:56 +0900, Won Kang wrote:
[]
> diff --git a/drivers/staging/gdm724x/TODO b/drivers/staging/gdm724x/TODO
[]
> @@ -1,2 +1,6 @@
> TODO:
> -- Clean up coding style to meet kernel standard.
> \ No newline at end of file
> +- Clean up coding style to meet kernel standard.
> +
>
Sometimes free_qos_entry() sometimes frees its argument. I have moved
the dereference of "entry" ahead on line to avoid a use after free.
Signed-off-by: Dan Carpenter
diff --git a/drivers/staging/gdm72xx/gdm_qos.c
b/drivers/staging/gdm72xx/gdm_qos.c
index b795353..cc36924 100644
--- a/drivers/
On Fri 19-07-13 12:23:05, K. Y. Srinivasan wrote:
> The current machinery for hot-adding memory requires having udev
> rules to bring the memory segments online. Export the necessary functionality
> to to bring the memory segment online without involving user space code.
Why? Who is going to use
On Mon, Jul 22, 2013 at 12:29:17AM -0700, Joe Perches wrote:
> On Mon, 2013-07-22 at 15:56 +0900, Won Kang wrote:
> []
> > diff --git a/drivers/staging/gdm724x/TODO b/drivers/staging/gdm724x/TODO
> []
> > @@ -1,2 +1,6 @@
> > TODO:
> > -- Clean up coding style to meet kernel standard.
> > \ No newl
Greg,
Can I expect to merge following patch series with your tree ?
http://driverdev.linuxdriverproject.org/pipermail/driverdev-devel/2013-July/039354.html
Or do you want me to rework on it as per your suggestions here :-
http://driverdev.linuxdriverproject.org/pipermail/driverdev-devel/2013-Jun
On Mon, Jul 22, 2013 at 06:43:18PM +0100, Rupesh Gujare wrote:
> Greg,
>
> Can I expect to merge following patch series with your tree ?
> http://driverdev.linuxdriverproject.org/pipermail/driverdev-devel/2013-July/039354.html
>
> Or do you want me to rework on it as per your suggestions here :-
From: Karlis Ogsts
In the situation that a writer fails to copy data from userspace it will reset
the write offset to the value it had before it went to sleep. This discarding
any messages written while aquiring the mutex.
Therefore the reset offset needs to be retrieved after acquiring the mute
From: Greg Kroah-Hartman [gre...@linuxfoundation.org]
Sent: 22 July 2013 18:55
To: Gujare, Rupesh
Cc: de...@linuxdriverproject.org; Joe Perches; linux-...@vger.kernel.org;
linux-ker...@vger.kernel.org
Subject: Re: [PATCH v2 5/5] staging: ozwpan: Rename Kbu
