netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: bpidoux@free.fr
Cc: ralf@linux-mips.org, netdev@vger.kernel.org, linux-hams@vger.kernel.org
Subject: Re: [PATCH] Wrong list_lock argument in rose_node seqops
Date: Fri, 02 May 2008 17:03:34 -0700 (PDT)	[thread overview]
Message-ID: <20080502.170334.97648357.davem@davemloft.net> (raw)
In-Reply-To: <200804302208.56925.bpidoux@free.fr>

From: Bernard Pidoux <bpidoux@free.fr>
Date: Wed, 30 Apr 2008 22:08:56 +0200

> In rose_node_start() as well as in rose_node_stop()
> __acquires() and spin_lock_bh() were wrongly passing
> rose_neigh_list_lock instead of rose_node_list_lock arguments.
> 
> Signed-off-by: Bernard Pidoux <f6bvp@amsat.org>

Applied, good catch.

Thanks Bernard.

      reply	other threads:[~2008-05-03  0:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-30 20:08 [PATCH] Wrong list_lock argument in rose_node seqops Bernard Pidoux
2008-05-03  0:03 ` David Miller [this message]

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=20080502.170334.97648357.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=bpidoux@free.fr \
    --cc=linux-hams@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).