From: Jeff Garzik <jgarzik@pobox.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "David S. Miller" <davem@davemloft.net>,
Linus Torvalds <torvalds@osdl.org>,
netdev@vger.kernel.org, Ayaz Abdulla <aabdulla@nvidia.com>
Subject: Re: [FORCEDETH]: Fix xmit_lock/netif_tx_lock after merge
Date: Tue, 20 Jun 2006 03:21:12 -0400 [thread overview]
Message-ID: <4497A1E8.3030708@pobox.com> (raw)
In-Reply-To: <20060620070450.GA12609@gondor.apana.org.au>
Herbert Xu wrote:
> Hi:
>
> [FORCEDETH]: Fix xmit_lock/netif_tx_lock after merge
>
> There has been an update to the forcedeth driver that added a few new
> uses of xmit_lock which is no longer meant to be used directly. This
> patch replaces them with netif_tx_lock_bh.
>
> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
ACK. I'll apply, if Linus doesn't pick this up...
Jeff
next prev parent reply other threads:[~2006-06-20 7:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 7:04 [FORCEDETH]: Fix xmit_lock/netif_tx_lock after merge Herbert Xu
2006-06-20 7:10 ` David Miller
2006-06-20 7:21 ` Jeff Garzik [this message]
2006-06-20 21:42 ` Linus Torvalds
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=4497A1E8.3030708@pobox.com \
--to=jgarzik@pobox.com \
--cc=aabdulla@nvidia.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
--cc=torvalds@osdl.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).