public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Bart Van Assche <bvanassche@acm.org>
Cc: linux-scsi@vger.kernel.org, scst-devel@lists.sourceforge.net,
	James.Bottomley@suse.de,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>
Subject: Re: [PATCH 2a/7] SCST core / sysfs interface
Date: Tue, 21 Dec 2010 11:01:29 -0800	[thread overview]
Message-ID: <20101221190129.GA10717@suse.de> (raw)
In-Reply-To: <201012211105.49590.bvanassche@acm.org>

On Tue, Dec 21, 2010 at 11:05:49AM +0100, Bart Van Assche wrote:
> Apparently patch 2/7 did not make it to the linux-scsi mailing list, probably
> because it was too big. So I'm resending the part of that patch that underwent
> the most changes since the previous time the SCST core was posted, namely the
> sysfs interface. Please let me know if other parts of the core should be posted
> again for review on the linux-scsi mailing list too.
> 
> This is what has been changed in the sysfs code since the previous time the
> SCST core was posted for review:
> - Instead of creating kernel objects in /sys/kernel/scst_tgt, the
>   bus/driver/device infastructure is now used.
> - The sysfs worker thread has been eliminated.
> -  A locking strategy for scst_mutex versus sysfs locking has been defined.
> - Several races between registration and unregistration functions have been fixed.
> - Several wait loops and state variables have been eliminated.
> 
> Signed-off-by: Bart Van Assche <bvanassche@acm.org>
> Cc: Greg Kroah-Hartman <gregkh@suse.de>
> Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> 
> diff --git a/Documentation/scst/SysfsRules b/Documentation/scst/SysfsRules

That's fine, but you need to properly create the files in
Documentation/ABI for your sysfs files.  Please do that as well.

thanks,

greg k-h

  reply	other threads:[~2010-12-21 19:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-21 10:05 [PATCH 2a/7] SCST core / sysfs interface Bart Van Assche
2010-12-21 19:01 ` Greg KH [this message]
2010-12-21 19:03 ` Greg KH
2010-12-22 12:41   ` Bart Van Assche
2010-12-22 19:32     ` Greg KH

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=20101221190129.GA10717@suse.de \
    --to=gregkh@suse.de \
    --cc=James.Bottomley@suse.de \
    --cc=bvanassche@acm.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=scst-devel@lists.sourceforge.net \
    /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