All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Mick <dan.mick@inktank.com>
To: Dan Mick <dan.mick@inktank.com>, stgt@vger.kernel.org
Subject: Re: [PATCH] add --bsopts flag, pass to bs_init()
Date: Thu, 17 Oct 2013 19:00:59 -0700	[thread overview]
Message-ID: <5260965B.90002@inktank.com> (raw)
In-Reply-To: <1381539243-13245-1-git-send-email-dan.mick@inktank.com>

ping

On 10/11/2013 05:54 PM, Dan Mick wrote:
> This patch implements the generic mechanism of passing backing-store-
> specific options to the backing store module's bs_init entry point.
> Each backing-store module gets a new parameter, char *bsopts,
> added to its bs_init.
>
> No semantics or even syntax are imposed on the option string, other
> than that commas are not permitted, because tgtadm communicates to
> tgtd using a block of key=val,key=val,key=val options, and there's
> no provision for escaping commas.
>
> tgtadm.8 is updated as well
>
> Dan Mick (1):
>    Add bsopts flag
>
>   doc/tgtadm.8.xml  |   20 +++++++++++++++++---
>   scripts/tgt-admin |   13 ++++++++++++-
>   usr/bs_aio.c      |    2 +-
>   usr/bs_rbd.c      |    3 ++-
>   usr/bs_rdwr.c     |    2 +-
>   usr/bs_sg.c       |    2 +-
>   usr/bs_sheepdog.c |    2 +-
>   usr/bs_ssc.c      |    2 +-
>   usr/spc.c         |    3 ++-
>   usr/target.c      |   12 +++++++++---
>   usr/tgtadm.c      |   18 +++++++++++++-----
>   usr/tgtd.h        |    2 +-
>   12 files changed, 61 insertions(+), 20 deletions(-)
>

       reply	other threads:[~2013-10-18  2:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1381539243-13245-1-git-send-email-dan.mick@inktank.com>
2013-10-18  2:00 ` Dan Mick [this message]
2013-10-20 12:53   ` [PATCH] add --bsopts flag, pass to bs_init() Hitoshi Mitake
2013-10-21  1:54   ` FUJITA Tomonori
2013-10-22 20:35     ` Dan Mick

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=5260965B.90002@inktank.com \
    --to=dan.mick@inktank.com \
    --cc=stgt@vger.kernel.org \
    /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.