From: "David S. Miller" <davem@davemloft.net>
To: linville@tuxdriver.com
Cc: netdev@vger.kernel.org, linux-tr@linuxtr.net, mikep@linuxtr.net,
jgarzik@pobox.com, fubar@us.ibm.com,
linux-kernel@vger.kernel.org
Subject: Re: [patch 2.6.13-rc6] net/802/tr: use interrupt-safe locking
Date: Wed, 17 Aug 2005 15:00:47 -0700 (PDT) [thread overview]
Message-ID: <20050817.150047.64537724.davem@davemloft.net> (raw)
In-Reply-To: <20050817204959.GA20186@tuxdriver.com>
From: "John W. Linville" <linville@tuxdriver.com>
Date: Wed, 17 Aug 2005 16:49:59 -0400
> Change operations on rif_lock from spin_{un}lock_bh to
> spin_{un}lock_irq{save,restore} equivalents. Some of the
> rif_lock critical sections are called from interrupt context via
> tr_type_trans->tr_add_rif_info. The TR NIC drivers call tr_type_trans
> from their packet receive handlers.
Applied, I'll try to get this into 2.6.13, but it may have
to wait for 2.6.14
prev parent reply other threads:[~2005-08-17 22:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <linville@tuxdriver.com>
2005-08-17 20:49 ` [patch 2.6.13-rc6] net/802/tr: use interrupt-safe locking John W. Linville
2005-08-17 21:48 ` Jay Vosburgh
2005-08-18 1:55 ` John W. Linville
2005-08-21 8:38 ` Andrew Morton
2005-08-17 22:00 ` David S. 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=20050817.150047.64537724.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=fubar@us.ibm.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tr@linuxtr.net \
--cc=linville@tuxdriver.com \
--cc=mikep@linuxtr.net \
--cc=netdev@vger.kernel.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).