target-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Christie <mchristi@redhat.com>
To: target-devel@vger.kernel.org
Subject: [PATCH 00/20] tcmu update
Date: Wed, 25 Oct 2017 16:47:10 +0000	[thread overview]
Message-ID: <1508950050-10120-1-git-send-email-mchristi@redhat.com> (raw)

Hey Nick,

The following patches were made over your for-next branch on target-pending.

Patches 1 -3 are ok for the next merge window:

- Patches 1 - 2 are misc fixes/changes.
- Patch 3 is just a cleanup to use the proper macro.

Patches 4 - 20 were posted later and have not been on the list
for as long and so maybe are better for the next-next merge
window.

- Patch 4 fixes the SCSI value that TCM_LOGICAL_UNIT_COMMUNICATION_FAILURE
is converted to. It is needed by patches 5 - 20.
- Patch 5 - 18 fix bugs in tcmu's ring buffer code.
- Patch 18 - 20 allow you to configure the size of the ring buffer
and how long we wait for ring memory.



             reply	other threads:[~2017-10-25 16:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-25 16:47 Mike Christie [this message]
2017-10-29 16:41 ` [PATCH 00/20] tcmu update Mike Christie

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=1508950050-10120-1-git-send-email-mchristi@redhat.com \
    --to=mchristi@redhat.com \
    --cc=target-devel@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 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).