From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Jinyoung CHOI <j-young.choi@samsung.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
"hch@lst.de" <hch@lst.de>,
"kbusch@kernel.org" <kbusch@kernel.org>,
"axboe@fb.com" <axboe@fb.com>,
"sagi@grimberg.me" <sagi@grimberg.me>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"chaitanyak@nvidia.com" <chaitanyak@nvidia.com>
Subject: Re: (2) (2) [PATCH 2/2] nvme-pci: fix metadata mapping length
Date: Wed, 12 Apr 2023 22:26:04 -0400 [thread overview]
Message-ID: <yq17cuga57p.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20230413021931epcms2p3bfbfbcd26e2732138bd66e3d9943d45c@epcms2p3> (Jinyoung CHOI's message of "Thu, 13 Apr 2023 11:19:31 +0900")
Jinyoung,
> When merging is performed in bio_integrity_add_page(), I think SG
> functions for integrity will be able to be modified more concisely. It
> was just the reason. :) If you are okay, can I try to modify it to
> solve the problem with add_page?
Yes, go ahead.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2023-04-13 2:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230412052443epcms2p836b669a12c4e81368bec2cd340656f73@epcms2p8>
2023-04-12 5:24 ` [PATCH 2/2] nvme-pci: fix metadata mapping length Jinyoung CHOI
2023-04-12 6:57 ` hch
2023-04-12 7:12 ` Jinyoung CHOI
2023-04-12 11:49 ` (2) " hch
2023-04-13 1:37 ` Martin K. Petersen
2023-04-13 2:19 ` Jinyoung CHOI
2023-04-13 2:26 ` Martin K. Petersen [this message]
2023-04-13 1:34 ` Martin K. Petersen
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=yq17cuga57p.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=axboe@fb.com \
--cc=chaitanyak@nvidia.com \
--cc=hch@lst.de \
--cc=j-young.choi@samsung.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox