virtio-blk: typo: Capitalization in Device Initialization item
PATCH 1/1 virtio-blk: typo: Capitalization in Device Initialization item
--- content.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
content.tex +1 -1
@@ -3969,7 +3969,7 @@ \subsection{Device Initialization}\label{sec:Device Types / Block Device / Devic segments for the block driver to use. \field{discard_sector_alignment} can be used by OS when splitting a request based on alignment. -\item if the VIRTIO_BLK_F_WRITE_ZEROES feature is negotiated, +\item If the VIRTIO_BLK_F_WRITE_ZEROES feature is negotiated, \field{max_write_zeroes_sectors} and \field{max_write_zeroes_seg} can be read to determine the maximum write zeroes sectors and maximum number of write zeroes segments for the block driver to use.
Signature · 18 lines
2.16.5 This publicly archived list offers a means to provide input to the OASIS Virtual I/O Device (VIRTIO) TC. In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting. Subscribe: [email protected] Unsubscribe: [email protected] List help: [email protected] List archive: https://lists.oasis-open.org/archives/virtio-comment/ Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists Committee: https://www.oasis-open.org/committees/virtio/ Join OASIS: https://www.oasis-open.org/join/
Quoted 4 lines · Eugenio Pérez
Signed-off-by Eugenio Pérez <[email protected]>--- content.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Hi there.
Is there any further action needed to merge this?
Thanks!
Quoted 8 lines · Stefan Hajnoczi
Quoted 4 lines · Eugenio Pérez
Signed-off-by Eugenio Pérez <[email protected]>--- content.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)Reviewed-by Stefan Hajnoczi <[email protected]>
This publicly archived list offers a means to provide input to the OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting.
Subscribe: [email protected]
Unsubscribe: [email protected]
List help: [email protected]
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
Quoted 1 line · Eugenio Perez Martin
Is there any further action needed to merge this?
Yes, a GitHub issue needs to be created. I have done this for you.
Ok, all the future patches will have the correspond github issue.
Thanks!
Quoted 7 lines · Stefan Hajnoczi
Quoted 1 line · Eugenio Perez Martin
Is there any further action needed to merge this?
Yes, a GitHub issue needs to be created. I have done this for you.
This publicly archived list offers a means to provide input to the OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting.
Subscribe: [email protected]
Unsubscribe: [email protected]
List help: [email protected]
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
Quoted 1 line · Eugenio Perez Martin
Ok, all the future patches will have the correspond github issue.
Actually, in another recent thread Michael Tsirkin said there is an exception for typo fixes. They don't require a vote and he can merge them directly. I think in the case of this patch series all that was required was a ping email in case Michael forgot about this patch.
Stefan