All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
To: linux-nvme@lists.infradead.org
Cc: hch@lst.de, sagi@grimberg.me,
	Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
Subject: [PATCH 0/4] nvme-fabrics: remove struct zeroout memset calls
Date: Mon, 14 Jun 2021 19:45:50 -0700	[thread overview]
Message-ID: <20210615024554.42585-1-chaitanya.kulkarni@wdc.com> (raw)

Hi,

While reviewing the code I did removed the calls to zero out structures
using memset() for the lio target, which are reviewed and accepted in
the linux kernel tree. (see [1])

This patch series is based on the same cleanup pattern for NVMe host.
This will allow us to have uniform pattern in the future code review to
avoid similar calls which seems unnecessary.

If this is accepted I'll gradually convert the rest of the host code
mainly core and pci.

-ck

Chaitanya Kulkarni (4):
  nvme-fabrics: remove memset in nvmf_reg_read64()
  nvme-fabrics: remove memset in nvmf_reg_write32()
  nvme-fabrics: remove memset in connect admin q
  nvme-fabrics: remove memset in connect io q

 drivers/nvme/host/fabrics.c | 12 ++++--------
 1 file changed, 4 insertions(+), 8 deletions(-)

[1] https://lore.kernel.org/linux-scsi/20210228055645.22253-1-chaitanya.kulkarni@wdc.com/
https://lore.kernel.org/linux-scsi/20210228055645.22253-13-chaitanya.kulkarni@wdc.com/
https://lore.kernel.org/linux-scsi/20210228055645.22253-14-chaitanya.kulkarni@wdc.com/
https://lore.kernel.org/linux-scsi/20210228055645.22253-15-chaitanya.kulkarni@wdc.com/
https://lore.kernel.org/linux-scsi/20210228055645.22253-16-chaitanya.kulkarni@wdc.com/
https://lore.kernel.org/linux-scsi/20210228055645.22253-17-chaitanya.kulkarni@wdc.com/
https://lore.kernel.org/linux-scsi/20210228055645.22253-18-chaitanya.kulkarni@wdc.com/
https://lore.kernel.org/linux-scsi/20210228055645.22253-19-chaitanya.kulkarni@wdc.com/

-- 
2.22.1


_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

             reply	other threads:[~2021-06-15 16:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-15  2:45 Chaitanya Kulkarni [this message]
2021-06-15  2:45 ` [PATCH 1/4] nvme-fabrics: remove memset in nvmf_reg_read64() Chaitanya Kulkarni
2021-06-15  2:45 ` [PATCH 2/4] nvme-fabrics: remove memset in nvmf_reg_write32() Chaitanya Kulkarni
2021-06-15  2:45 ` [PATCH 3/4] nvme-fabrics: remove memset in connect admin q Chaitanya Kulkarni
2021-06-15  2:45 ` [PATCH 4/4] nvme-fabrics: remove memset in connect io q Chaitanya Kulkarni
2021-06-15 16:19 ` [PATCH 0/4] nvme-fabrics: remove struct zeroout memset calls Christoph Hellwig
2021-06-15 18:42 ` Keith Busch
2021-06-15 20:07   ` Chaitanya Kulkarni

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=20210615024554.42585-1-chaitanya.kulkarni@wdc.com \
    --to=chaitanya.kulkarni@wdc.com \
    --cc=hch@lst.de \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /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.