From: David Miller <davem@davemloft.net>
To: pidoux@ccr.jussieu.fr
Cc: ralf@linux-mips.org, linux-kernel@vger.kernel.org,
linux-hams@vger.kernel.org
Subject: Re: [PATCH] rose_node_list_lock was not released before returning to user space
Date: Sat, 19 Apr 2008 18:38:34 -0700 (PDT) [thread overview]
Message-ID: <20080419.183834.238901544.davem@davemloft.net> (raw)
In-Reply-To: <480A6034.1080806@ccr.jussieu.fr>
From: Bernard Pidoux <pidoux@ccr.jussieu.fr>
Date: Sat, 19 Apr 2008 23:12:20 +0200
> I have already submited this patch on January 11, 2008.
> As the bug is still present, I resend it.
I'll apply this fix, thanks a lot Bernard.
next prev parent reply other threads:[~2008-04-20 1:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-19 21:12 [PATCH] rose_node_list_lock was not released before returning to user space Bernard Pidoux
2008-04-20 1:38 ` David Miller [this message]
2008-04-20 1:40 ` David Miller
2008-04-20 17:09 ` [PATCH] soft lockup rose_node_list_lock Bernard Pidoux
2008-04-20 22:59 ` David Miller
2008-04-21 20:27 ` Bernard Pidoux
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=20080419.183834.238901544.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-hams@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pidoux@ccr.jussieu.fr \
--cc=ralf@linux-mips.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox