From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: linux-scsi@vger.kernel.org, jth@kernel.org, rt@linutronix.de,
jejb@linux.vnet.ibm.com,
"Martin K . Petersen" <martin.petersen@oracle.com>,
QLogic-Storage-Upstream@qlogic.com,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH 1/4] scsi: bnx2fc: convert per-CPU thread to kworker
Date: Wed, 20 Jul 2016 14:07:19 +0200 [thread overview]
Message-ID: <323040c8-3b63-7e49-a492-e071610459fd@linutronix.de> (raw)
In-Reply-To: <20160720110421.5ocuquyqki2uggg4@c203.arch.suse.de>
On 07/20/2016 01:04 PM, Johannes Thumshirn wrote:
> Hi Sebastian,
Hi Johannes,
> I've tried to test your series and unfortunately I encountered the following
> oops.
thanks for testing.
…
>
> I'll try to narrow it down to the specific patch, but currently I'm a bit
> busy, sorry.
I looked over the patch and noticed nothing. It was possible to run the
worker but somehow the spinlock exploded.
>
> Johannes
>
Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-07-20 12:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 16:08 [PATCH 1/4] scsi: bnx2fc: convert per-CPU thread to kworker Sebastian Andrzej Siewior
2016-07-05 16:08 ` [PATCH 2/4] scsi: bnx2fc: clean up header definitions Sebastian Andrzej Siewior
2016-07-05 16:08 ` [PATCH 3/4] scsi: bnx2fc: annoate unlock + release for sparse Sebastian Andrzej Siewior
2016-07-05 16:08 ` [PATCH 4/4] scsi: bnx2fc: convert bnx2fc_l2_rcv_thread() to worker Sebastian Andrzej Siewior
2016-07-05 16:20 ` [PATCH 4/4 v2] " Sebastian Andrzej Siewior
2016-07-20 11:04 ` [PATCH 1/4] scsi: bnx2fc: convert per-CPU thread to kworker Johannes Thumshirn
2016-07-20 12:07 ` Sebastian Andrzej Siewior [this message]
2016-07-20 12:13 ` Johannes Thumshirn
2016-08-12 11:00 ` Sebastian Andrzej Siewior
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=323040c8-3b63-7e49-a492-e071610459fd@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=QLogic-Storage-Upstream@qlogic.com \
--cc=hch@lst.de \
--cc=jejb@linux.vnet.ibm.com \
--cc=jth@kernel.org \
--cc=jthumshirn@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=rt@linutronix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.