All of lore.kernel.org
 help / color / mirror / Atom feed
From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH v2 0/2] Fixes for issues detected by static analyzers
Date: Thu, 11 Oct 2018 07:55:27 +0200	[thread overview]
Message-ID: <20181011055527.GA30276@lst.de> (raw)
In-Reply-To: <20181010150820.203745-1-bvanassche@acm.org>

Thanks a lot Bart,

applied to nvme-4.20.

      parent reply	other threads:[~2018-10-11  5:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-10 15:08 [PATCH v2 0/2] Fixes for issues detected by static analyzers Bart Van Assche
2018-10-10 15:08 ` [PATCH v2 1/2] nvme-core: Make implicit seed truncation explicit Bart Van Assche
2018-10-10 15:34   ` Keith Busch
2018-10-10 15:08 ` [PATCH v2 2/2] nvmet-fcloop: Suppress a compiler warning Bart Van Assche
2018-10-10 15:57   ` James Smart
2018-10-10 16:35     ` Bart Van Assche
2018-10-11  5:55 ` Christoph Hellwig [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=20181011055527.GA30276@lst.de \
    --to=hch@lst.de \
    /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.