From: Christoph Hellwig <hch@lst.de>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Christoph Hellwig <hch@lst.de>,
linux-scsi@vger.kernel.org, Johannes Thumshirn <jth@kernel.org>,
rt@linutronix.de,
"James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
QLogic-Storage-Upstream@qlogic.com,
Chad Dupuis <chad.dupuis@qlogic.com>
Subject: Re: [PATCH 1/5] scsi: bnx2i: convert to kworker
Date: Fri, 18 Nov 2016 15:55:04 +0100 [thread overview]
Message-ID: <20161118145504.GA9405@lst.de> (raw)
In-Reply-To: <20161118143932.jqjjwa6tjzyxwtup@linutronix.de>
On Fri, Nov 18, 2016 at 03:39:32PM +0100, Sebastian Andrzej Siewior wrote:
> On 2016-11-18 13:56:22 [+0100], Christoph Hellwig wrote:
> > still says kwork in the subject..
>
> I was thinking about this before sending it out. But then it uses the
> generic workqueue / kworker and a custom kthread like it did before.
> What would you prefer to call it then? Just workqueue?
Just workqueue.
next prev parent reply other threads:[~2016-11-18 14:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 10:10 bnx2i + bnx2fc: convert to generic workqueue Sebastian Andrzej Siewior
2016-11-18 10:10 ` [PATCH 1/5] scsi: bnx2i: convert to kworker Sebastian Andrzej Siewior
2016-11-18 12:56 ` Christoph Hellwig
2016-11-18 14:39 ` Sebastian Andrzej Siewior
2016-11-18 14:55 ` Christoph Hellwig [this message]
2016-11-18 10:10 ` [PATCH 2/5] scsi: bnx2fc: convert per-CPU thread " Sebastian Andrzej Siewior
2016-11-18 10:10 ` [PATCH 3/5] scsi: bnx2fc: clean up header definitions Sebastian Andrzej Siewior
2016-11-18 10:10 ` [PATCH 4/5] scsi: bnx2fc: annoate unlock + release for sparse Sebastian Andrzej Siewior
2016-11-18 10:10 ` [PATCH 5/5] scsi: bnx2fc: convert bnx2fc_l2_rcv_thread() to worker 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=20161118145504.GA9405@lst.de \
--to=hch@lst.de \
--cc=QLogic-Storage-Upstream@qlogic.com \
--cc=bigeasy@linutronix.de \
--cc=chad.dupuis@qlogic.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=jth@kernel.org \
--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 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).