From: Christoph Hellwig <hch@lst.de>
To: Hannes Reinecke <hare@suse.de>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
Christoph Hellwig <hch@lst.de>,
James Bottomley <james.bottomley@hansenpartnership.com>,
Johannes Thumshirn <jthumshirn@suse.com>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH 2/2] scsi_transport_fc: Implement 'async_user_scan' module parameter
Date: Tue, 1 Mar 2016 14:15:20 +0100 [thread overview]
Message-ID: <20160301131520.GB7786@lst.de> (raw)
In-Reply-To: <1456127462-2817-3-git-send-email-hare@suse.de>
Bah. Async scanning seems useful, but it shouldn't be a module option
that breaks exsiting users of the attribute, and it shouldn't be in
the FC transport class.
Just add a new async_scan attribute that works like scan, but works
asynchronously in the core.
Or figure out if we can overload the already parsed but ignored
junk argument in the scan attribute to accept an 'a' for async?
next prev parent reply other threads:[~2016-03-01 13:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 7:51 [PATCH 0/2][RESEND] scsi_transport_fc: LUN masking Hannes Reinecke
2016-02-22 7:51 ` [PATCH 1/2] scsi_transport_fc: implement 'disable_target_scan' module parameter Hannes Reinecke
2016-03-01 9:06 ` Johannes Thumshirn
2016-03-01 13:12 ` Christoph Hellwig
2016-03-02 5:59 ` Hannes Reinecke
2016-03-02 9:18 ` Christoph Hellwig
2016-03-02 9:35 ` Hannes Reinecke
2016-02-22 7:51 ` [PATCH 2/2] scsi_transport_fc: Implement 'async_user_scan' " Hannes Reinecke
2016-03-01 5:45 ` Seymour, Shane M
2016-03-01 9:07 ` Johannes Thumshirn
2016-03-01 13:15 ` Christoph Hellwig [this message]
2016-02-22 11:39 ` [PATCH 0/2][RESEND] scsi_transport_fc: LUN masking Seymour, Shane M
2016-02-23 10:21 ` Hannes Reinecke
2016-02-24 0:35 ` Seymour, Shane M
2016-03-01 19:54 ` Ewan Milne
2016-03-02 6:35 ` Hannes Reinecke
-- strict thread matches above, loose matches on Subject: below --
2015-11-11 10:34 [PATCH 0/2] " Hannes Reinecke
2015-11-11 10:34 ` [PATCH 2/2] scsi_transport_fc: Implement 'async_user_scan' module parameter Hannes Reinecke
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=20160301131520.GB7786@lst.de \
--to=hch@lst.de \
--cc=hare@suse.de \
--cc=james.bottomley@hansenpartnership.com \
--cc=jthumshirn@suse.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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 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.