From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: target-devel@vger.kernel.org
Subject: Re: [PATCH 0/3] Three reliability improvements
Date: Wed, 13 Nov 2019 01:15:39 +0000 [thread overview]
Message-ID: <yq1sgmsshj8.fsf@oracle.com> (raw)
In-Reply-To: <20191112035752.8338-1-bvanassche@acm.org>
Bart,
> - The patch that declares target_release_reservation() static has been
> left out because a patch in this series introduces a call to that
> function outside the file in which that function has been defined.
OK, I'll drop it again. Thought this series replaced patch two of the
first.
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2019-11-13 1:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 3:57 [PATCH 0/3] Three reliability improvements Bart Van Assche
2019-11-12 17:05 ` Bart Van Assche
2019-11-13 1:15 ` Martin K. Petersen [this message]
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=yq1sgmsshj8.fsf@oracle.com \
--to=martin.petersen@oracle.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