From: Christoph Hellwig <hch@infradead.org>
To: Ondrej Kozina <okozina@redhat.com>
Cc: linux-block@vger.kernel.org, bluca@debian.org,
gmazyland@gmail.com, axboe@kernel.dk, hch@infradead.org,
brauner@kernel.org, jonathan.derrick@linux.dev
Subject: Re: [PATCH v2 1/1] sed-opal: geometry feature reporting command
Date: Tue, 11 Apr 2023 05:31:23 -0700 [thread overview]
Message-ID: <ZDVTG361r+EkYjIf@infradead.org> (raw)
In-Reply-To: <20230411090931.9193-2-okozina@redhat.com>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2023-04-11 12:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 13:19 [PATCH 0/1] sed-opal: geometry feature reporting command Ondrej Kozina
2023-04-06 13:19 ` [PATCH 1/1] " Ondrej Kozina
2023-04-06 20:32 ` Milan Broz
2023-04-11 9:05 ` Ondrej Kozina
2023-04-11 9:09 ` [PATCH v2 0/1] " Ondrej Kozina
2023-04-11 9:09 ` [PATCH v2 1/1] " Ondrej Kozina
2023-04-11 12:31 ` Christoph Hellwig [this message]
2023-04-11 13:28 ` Christian Brauner
2023-04-11 14:46 ` Milan Broz
2023-04-19 7:33 ` [PATCH v2 0/1] " Ondrej Kozina
2023-04-19 20:07 ` Jens Axboe
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=ZDVTG361r+EkYjIf@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=bluca@debian.org \
--cc=brauner@kernel.org \
--cc=gmazyland@gmail.com \
--cc=jonathan.derrick@linux.dev \
--cc=linux-block@vger.kernel.org \
--cc=okozina@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).