All of lore.kernel.org
 help / color / mirror / Atom feed
From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH v4 0/3] Improve readbility of NVME "wwid" attribute (target side)
Date: Wed, 16 Aug 2017 01:12:01 -0700	[thread overview]
Message-ID: <20170816081201.GD11377@infradead.org> (raw)
In-Reply-To: <20170814201239.15255-1-mwilck@suse.com>

Thanks, applied patch 1 to nvme-4.13, and the rest to nvme-4.14.

Btw, for future patches please use the driver name as prefix and
not a function name.

WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Martin Wilck <mwilck@suse.com>
Cc: Christoph Hellwig <hch@lst.de>,
	Keith Busch <keith.busch@intel.com>,
	Sagi Grimberg <sagi@grimberg.me>, Martin Wilck <mwilck@suse.de>,
	linux-kernel@vger.kernel.org, Hannes Reinecke <hare@suse.de>,
	linux-nvme@lists.infradead.org,
	Johannes Thumshirn <jthumshirn@suse.de>
Subject: Re: [PATCH v4 0/3] Improve readbility of NVME "wwid" attribute (target side)
Date: Wed, 16 Aug 2017 01:12:01 -0700	[thread overview]
Message-ID: <20170816081201.GD11377@infradead.org> (raw)
In-Reply-To: <20170814201239.15255-1-mwilck@suse.com>

Thanks, applied patch 1 to nvme-4.13, and the rest to nvme-4.14.

Btw, for future patches please use the driver name as prefix and
not a function name.

  parent reply	other threads:[~2017-08-16  8:12 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-20 16:33 [PATCH v3 0/3] Improve readbility of NVME "wwid" attribute Martin Wilck
2017-07-20 16:33 ` Martin Wilck
2017-07-20 16:34 ` [PATCH v3 1/3] string.h: add memcpy_and_pad() Martin Wilck
2017-07-20 16:34   ` Martin Wilck
2017-07-22  3:45   ` kbuild test robot
2017-07-22  3:45     ` kbuild test robot
2017-07-23 18:18   ` kbuild test robot
2017-07-23 18:18     ` kbuild test robot
2017-07-20 16:34 ` [PATCH v3 2/3] nvmet: identify controller: improve standard compliance Martin Wilck
2017-07-20 16:34   ` Martin Wilck
2017-07-20 16:34 ` [PATCH v3 3/3] nvme: wwid_show: strip trailing 0-bytes Martin Wilck
2017-07-20 16:34   ` Martin Wilck
2017-07-20 20:11   ` Keith Busch
2017-07-20 20:11     ` Keith Busch
2017-08-10  8:45   ` Christoph Hellwig
2017-08-10  8:45     ` Christoph Hellwig
2017-08-14 20:12     ` [PATCH v4 0/3] Improve readbility of NVME "wwid" attribute (target side) Martin Wilck
2017-08-14 20:12       ` Martin Wilck
2017-08-14 20:12       ` [PATCH v4 1/3] nvmet_execute_identify_ctrl: don't overwrite with 0-bytes Martin Wilck
2017-08-14 20:12         ` Martin Wilck
2017-08-14 20:12       ` [PATCH v4 2/3] string.h: add memcpy_and_pad() Martin Wilck
2017-08-14 20:12         ` Martin Wilck
2017-09-05  7:28         ` Arnd Bergmann
2017-09-05  7:28           ` Arnd Bergmann
2017-09-05 18:18           ` Martin Wilck
2017-09-05 18:18             ` Martin Wilck
2017-09-05 18:23           ` [PATCH] string.h: un-fortify memcpy_and_pad Martin Wilck
2017-09-05 18:23             ` Martin Wilck
2017-09-05 19:26             ` Arnd Bergmann
2017-09-05 19:26               ` Arnd Bergmann
2017-09-06 13:02               ` Arnd Bergmann
2017-09-06 13:02                 ` Arnd Bergmann
2017-08-14 20:12       ` [PATCH v4 3/3] nvmet_execute_identify_ctrl: use memcpy_and_pad() Martin Wilck
2017-08-14 20:12         ` Martin Wilck
2017-08-15  9:10       ` [PATCH v4 0/3] Improve readbility of NVME "wwid" attribute (target side) Sagi Grimberg
2017-08-15  9:10         ` Sagi Grimberg
2017-08-16  8:12       ` Christoph Hellwig [this message]
2017-08-16  8:12         ` Christoph Hellwig

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=20170816081201.GD11377@infradead.org \
    --to=hch@infradead.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.