From: David Miller <davem@davemloft.net>
To: error27@gmail.com
Cc: sathyap@serverengines.com, subbus@serverengines.com,
sarveshwarb@serverengines.com, ajitk@serverengines.com,
netdev@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch 1/2] be2net: add unlock on error path
Date: Sat, 29 May 2010 00:20:10 -0700 (PDT) [thread overview]
Message-ID: <20100529.002010.123974681.davem@davemloft.net> (raw)
In-Reply-To: <20100526144634.GL22515@bicker>
From: Dan Carpenter <error27@gmail.com>
Date: Wed, 26 May 2010 16:46:35 +0200
> The unlock accidentally got removed from the error path in dd131e76e5:
> "be2net: Bug fix to avoid disabling bottom half during firmware upgrade."
>
> Signed-off-by: Dan Carpenter <error27@gmail.com>
Applied.
prev parent reply other threads:[~2010-05-29 7:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 14:46 [patch 1/2] be2net: add unlock on error path Dan Carpenter
2010-05-27 6:31 ` Sarveshwar Bandi
2010-05-29 7:20 ` 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=20100529.002010.123974681.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ajitk@serverengines.com \
--cc=error27@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sarveshwarb@serverengines.com \
--cc=sathyap@serverengines.com \
--cc=subbus@serverengines.com \
/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).