All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gabriel Krisman Bertazi <krisman@collabora.com>
To: Lee Duncan <leeman.duncan@gmail.com>
Cc: open-iscsi <open-iscsi@googlegroups.com>,
	Lee Duncan <lduncan@suse.com>,
	martin.petersen@oracle.com, linux-scsi@vger.kernel.org,
	Bharath Ravi <rbharath@google.com>,
	kernel@collabora.com, Michael Christie <mchristi@redhat.com>,
	Bart Van Assche <bvanassche@acm.org>,
	Dave Clausen <dclausen@google.com>, Nick Black <nlb@google.com>,
	Vaibhav Nagarnaik <vnagarnaik@google.com>,
	Anatol Pomazau <anatol@google.com>,
	Tahsin Erdogan <tahsin@google.com>,
	Frank Mayhar <fmayhar@google.com>, Junho Ryu <jayr@google.com>,
	Khazhismel Kumykov <khazhy@google.com>
Subject: Re: [PATCH RESEND v4] iscsi: Perform connection failure entirely in kernel space
Date: Sat, 25 Jan 2020 12:46:23 -0500	[thread overview]
Message-ID: <8536c3ctu8.fsf@collabora.com> (raw)
In-Reply-To: <F29720C3-86AC-407A-8255-9186E3AE0676@gmail.com> (Lee Duncan's message of "Sat, 25 Jan 2020 09:22:02 -0800")

Lee Duncan <leeman.duncan@gmail.com> writes:

> I’m sorry if it didn’t get through, but I sent a Reviewed-by update and the end of last week.
>
> I looked over the updates, and I said that they look good to me, and I said please re-add my:
>
> Reviewed-by: Lee Duncan <lduncan@suse.com <mailto:lduncan@suse.com>>

Hey,

Thank you very much for the quick response!  I checked here again and I didn't
get the previous email, but I see it made into the ML archive, so my apologies,
it must be something bad on my (or my employer's) setup.

Thanks,

-- 
Gabriel Krisman Bertazi

  parent reply	other threads:[~2020-01-25 17:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-25  6:19 [PATCH RESEND v4] iscsi: Perform connection failure entirely in kernel space Gabriel Krisman Bertazi
     [not found] ` <F29720C3-86AC-407A-8255-9186E3AE0676@gmail.com>
2020-01-25 17:46   ` Gabriel Krisman Bertazi [this message]
2020-01-28  3:20     ` Martin K. Petersen

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=8536c3ctu8.fsf@collabora.com \
    --to=krisman@collabora.com \
    --cc=anatol@google.com \
    --cc=bvanassche@acm.org \
    --cc=dclausen@google.com \
    --cc=fmayhar@google.com \
    --cc=jayr@google.com \
    --cc=kernel@collabora.com \
    --cc=khazhy@google.com \
    --cc=lduncan@suse.com \
    --cc=leeman.duncan@gmail.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=mchristi@redhat.com \
    --cc=nlb@google.com \
    --cc=open-iscsi@googlegroups.com \
    --cc=rbharath@google.com \
    --cc=tahsin@google.com \
    --cc=vnagarnaik@google.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.