linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: bvanassche@acm.org (Bart Van Assche)
Subject: nvmet: Kernel v4.19-rc4 circular locking complaint
Date: Thu, 27 Sep 2018 08:42:44 -0700	[thread overview]
Message-ID: <1538062964.226558.2.camel@acm.org> (raw)
In-Reply-To: <1b13d375-3ab4-4e95-ea3b-662ddba8bdf9@grimberg.me>

On Tue, 2018-09-25@22:38 -0700, Sagi Grimberg wrote:
> I think that moving release work to a private wq should help, does it
> make this complaint go away?

Hi Sagi,

Thanks for the patch. However, it seems like your patch got line-wrapped.
Can you resend it?

Thanks,

Bart.

$ patch -p1 < ~/Re\:_nvmet\:_Kernel_v4.19-rc4_circular_locking_complaint.mbox        
(Stripping trailing CRs from patch; use --binary to disable.)

patching file drivers/nvme/target/rdma.c

Hunk #1 FAILED at 122.

patch: **** malformed patch at line 129: rdma_cm_id *cm_id,

      reply	other threads:[~2018-09-27 15:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-20 17:49 nvmet: Kernel v4.19-rc4 circular locking complaint Bart Van Assche
2018-09-25 23:27 ` Christoph Hellwig
2018-09-26  5:38 ` Sagi Grimberg
2018-09-27 15:42   ` Bart Van Assche [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=1538062964.226558.2.camel@acm.org \
    --to=bvanassche@acm.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).