From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: "James E.J. Bottomley" <JBottomley@odin.com>,
"K. Y. Srinivasan" <kys@microsoft.com>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
devel@linuxdriverproject.org, ohering@suse.com,
jbottomley@parallels.com, hch@infradead.org,
linux-scsi@vger.kernel.org, apw@canonical.com,
jasowang@redhat.com
Subject: Re: [PATCH 0/3] scsi: Some miscellaneous fixes
Date: Tue, 29 Sep 2015 15:33:57 +0200 [thread overview]
Message-ID: <87h9md2vui.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <1442528938-3252-1-git-send-email-kys@microsoft.com> (K. Y. Srinivasan's message of "Thu, 17 Sep 2015 15:28:58 -0700")
"K. Y. Srinivasan" <kys@microsoft.com> writes:
[...]
>
> Vitaly Kuznetsov (2):
> scsi_scan: don't dump trace when scsi_prep_async_scan() is called
> twice
> scsi: introduce short_inquiry flag for broken host adapters
James,
I'm sorry for the annoyance but when I asked about these patches last
time you said we don't have them reviewed. Is it OK now when we have
signed-off-by: from K. Y. or do we need to ask someone else?
Thanks,
--
Vitaly
next prev parent reply other threads:[~2015-09-29 13:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 22:28 [PATCH 0/3] scsi: Some miscellaneous fixes K. Y. Srinivasan
2015-09-17 22:29 ` [PATCH 1/3] scsi_scan: don't dump trace when scsi_prep_async_scan() is called twice K. Y. Srinivasan
2015-09-17 22:29 ` K. Y. Srinivasan
2015-09-17 22:29 ` [PATCH 2/3] scsi: introduce short_inquiry flag for broken host adapters K. Y. Srinivasan
2015-09-17 22:29 ` K. Y. Srinivasan
2015-09-17 22:29 ` [PATCH RESEND 3/3] storvsc: Don't set the SRB_FLAGS_QUEUE_ACTION_ENABLE flag K. Y. Srinivasan
2015-09-29 13:33 ` Vitaly Kuznetsov [this message]
2015-10-01 19:57 ` [PATCH 0/3] scsi: Some miscellaneous fixes KY Srinivasan
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=87h9md2vui.fsf@vitty.brq.redhat.com \
--to=vkuznets@redhat.com \
--cc=JBottomley@odin.com \
--cc=apw@canonical.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=jasowang@redhat.com \
--cc=jbottomley@parallels.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=ohering@suse.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.