From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Dan Carpenter <error27@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
"open list:INTEL WIRELESS 39..." <linux-wireless@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: [patch -next] iwlegacy: fix up brokenness caused by cleanup
Date: Thu, 16 Jun 2011 10:14:27 +0200 [thread overview]
Message-ID: <20110616081426.GA2178@redhat.com> (raw)
In-Reply-To: <20110615131009.GD23739@shale.localdomain>
On Wed, Jun 15, 2011 at 04:10:10PM +0300, Dan Carpenter wrote:
> Patch 7f1f9742514 "iwlegacy: refactor iwl4965_mac_channel_switch"
> reversed a test and also it changed a spin_lock_irq() to
> spin_lock(). I assume the spin_lock change was a mistake because
> the unlock was left as spin_unlock_irq().
Thank you Dan!
Stanislaw
prev parent reply other threads:[~2011-06-16 8:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 13:10 [patch -next] iwlegacy: fix up brokenness caused by cleanup Dan Carpenter
2011-06-16 8:14 ` Stanislaw Gruszka [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=20110616081426.GA2178@redhat.com \
--to=sgruszka@redhat.com \
--cc=error27@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).