On Wed, Nov 07, 2012 at 01:20:41PM +0100, Marc Kleine-Budde wrote:
> On 11/07/2012 12:22 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD
> > Cc: Nicolas Ferre
> > Cc: linux-...@vger.kernel.org
> > Cc: linux-in...@vger.kernel.org
> > Cc: linux-...@vg
Commit f79b2d0f (USB: keyspan: fix NULL-pointer dereferences and
memory leaks) had a small typo which made the driver use wrong
offsets when mapping serial port private data. This results in
in a GPF when the port is opened.
Reported-by: Richard
Cc:
Cc: Johan Hovold
Signed-off-by: Bjørn Mork
Signed-off-by: Harvey Yang
---
drivers/staging/usbip/vhci_hcd.c | 80 +++---
1 files changed, 40 insertions(+), 40 deletions(-)
diff --git a/drivers/staging/usbip/vhci_hcd.c b/drivers/staging/usbip/vhci_hcd.c
index 620d1be..6771668 100644
--- a/drivers/staging/
Hi Jean-Christophe,
On 7 November 2012 12:22, Jean-Christophe PLAGNIOL-VILLARD
wrote:
> Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD
> Cc: Nicolas Ferre
> Cc: linux-...@vger.kernel.org
> Cc: linux-in...@vger.kernel.org
> Cc: linux-...@vger.kernel.org
> Cc: linux-...@vger.kernel.org
> Cc: net
On Sat, Nov 10, 2012 at 10:13 AM, Bjørn Mork wrote:
> Commit f79b2d0f (USB: keyspan: fix NULL-pointer dereferences and
> memory leaks) had a small typo which made the driver use wrong
> offsets when mapping serial port private data. This results in
> in a GPF when the port is opened.
>
> Reported
On Fri, Nov 9, 2012 at 11:14 PM, Richard Retanubun
wrote:
> On 29/10/12 06:14 PM, Alan Stern wrote:
>>
>> On Mon, 29 Oct 2012, Richard Retanubun wrote:
>>>
>>> Focusing down on one of the dumps:
>>>
>>> unreferenced object 0xd3849740 (size 8):
>>> comm "khubd", pid 1026, jiffies 232553037 (age
Hi,
On Fri, Nov 9, 2012 at 12:53 PM, Felipe Balbi wrote:
> Hi,
>
> On Fri, Nov 09, 2012 at 10:31:47AM +0100, Dmytro Milinevskyy wrote:
>> Hi Felipe,
>>
>> On Thu, Nov 8, 2012 at 8:30 PM, Felipe Balbi wrote:
>> > Hi,
>> >
>> > On Thu, Nov 08, 2012 at 08:07:57PM +0100, Dmytro Milinevskyy wrote:
>>
Hello,
I'm wondering how long it will be before this
patch appears in a 3.6.x release. Any idea?
Any opinion on whether a 3.4.x or 3.2.x kernel
would be better than 3.6.x for a production
network backup system (i.e. super critical)?
Or is 3.6 best? Running 3.1.8 at present.
Seeing the timeout
Bjørn:
I patched keyspan.c using your below supplied diff in 3.6.6 (I'm not
using git.) The patch WORKS for me. (I tested using minicom and the
two programs that usually access the Keyspan serial device.)
Thank you for the quick fix.
Will this show up in 3.6.7?
Richard
richj...@pacbell.net
On Sat, 10 Nov 2012 starlight.201...@binnacle.cx wrote:
> Hello,
>
> I'm wondering how long it will be before this
> patch appears in a 3.6.x release. Any idea?
Probably a week or two. It's up to Greg KH.
> Any opinion on whether a 3.4.x or 3.2.x kernel
> would be better than 3.6.x for a prod
At 08:37 PM 11/10/2012 -0500, Alan Stern wrote:
>Does the patch fix the problem?
Will let you and the list know. Want
to wait for a full kernel release.
The drives go active if the power to
the docks is toggled after they spin
up--going with that for now.
Will finish configuring the array
and o
11 matches
Mail list logo
