From: Philippe De Muyter <phdm@macqel.be>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: linux1394-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] firewire: core: no need to track irq flags in bm_work
Date: Tue, 22 Jun 2010 11:36:18 +0200 [thread overview]
Message-ID: <20100622093618.GC26304@frolo.macqel> (raw)
In-Reply-To: <tkrat.96072b90a5c06bb3@s5r6.in-berlin.de>
On Mon, Jun 21, 2010 at 11:23:52PM +0200, Stefan Richter wrote:
> This is a workqueue job and always entered with IRQs enabled.
did you mean 'disabled' ?
Philippe
>
> Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
> ---
> drivers/firewire/core-card.c | 15 +++++++--------
> 1 file changed, 7 insertions(+), 8 deletions(-)
>
> Index: b/drivers/firewire/core-card.c
> ===================================================================
> --- a/drivers/firewire/core-card.c
> +++ b/drivers/firewire/core-card.c
> @@ -239,7 +239,6 @@ static void fw_card_bm_work(struct work_
> struct fw_card *card = container_of(work, struct fw_card, work.work);
> struct fw_device *root_device, *irm_device;
> struct fw_node *root_node;
> - unsigned long flags;
> int root_id, new_root_id, irm_id, local_id;
> int gap_count, generation, grace, rcode;
> bool do_reset = false;
> @@ -247,10 +246,10 @@ static void fw_card_bm_work(struct work_
> bool root_device_is_cmc;
> bool irm_is_1394_1995_only;
>
> - spin_lock_irqsave(&card->lock, flags);
> + spin_lock_irq(&card->lock);
next prev parent reply other threads:[~2010-06-22 9:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 21:23 Stefan Richter
2010-06-21 21:24 ` [PATCH 2/2] firewire: cdev: fix fw_cdev_event_bus_reset.bm_node_id Stefan Richter
2010-06-22 9:36 ` Philippe De Muyter [this message]
2010-06-22 11:43 ` [PATCH 1/2] firewire: core: no need to track irq flags in bm_work Stefan Richter
2010-06-22 14:26 ` Philippe De Muyter
2010-06-22 18:39 ` Stefan Richter
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=20100622093618.GC26304@frolo.macqel \
--to=phdm@macqel.be \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=stefanr@s5r6.in-berlin.de \
/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
all inboxes | Powered by JetHome®