From: David Disseldorp <ddiss@suse.de>
To: target-devel@vger.kernel.org
Subject: Re: [PATCH] target/core: Avoid that a kernel oops can be triggered when an XCOPY command fails
Date: Mon, 05 Nov 2018 23:19:30 +0000 [thread overview]
Message-ID: <20181106001930.39cba3bd@suse.de> (raw)
In-Reply-To: <20181105184011.94041-1-bvanassche@acm.org>
On Mon, 5 Nov 2018 10:40:11 -0800, Bart Van Assche wrote:
> Avoid that a kernel oops can be triggered when an XCOPY command fails
FWIW, that should be COMPARE_AND_WRITE instead of XCOPY.
Cheers, David
prev parent reply other threads:[~2018-11-05 23:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 18:40 [PATCH] target/core: Avoid that a kernel oops can be triggered when an XCOPY command fails Bart Van Assche
2018-11-05 19:09 ` David Disseldorp
2018-11-05 23:19 ` David Disseldorp [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=20181106001930.39cba3bd@suse.de \
--to=ddiss@suse.de \
--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 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.