From: Jens Axboe <axboe@kernel.dk>
To: Revanth Rajashekar <revanth.rajashekar@intel.com>,
linux-block@vger.kernel.org
Cc: Jonathan Derrick <jonathan.derrick@intel.com>,
Scott Bauer <sbauer@plzdonthack.me>
Subject: Re: [PATCH v3 0/3] block: sed-opal: Code Cleanup Patches
Date: Tue, 20 Aug 2019 09:35:09 -0600 [thread overview]
Message-ID: <2a4299af-2310-b34d-7129-90ab592976fe@kernel.dk> (raw)
In-Reply-To: <20190820153051.24704-1-revanth.rajashekar@intel.com>
On 8/20/19 9:30 AM, Revanth Rajashekar wrote:
> This series of patch is a cleanup for sed-opal in kernel 5.4. It
> 1. Adds/removes spaces.
> 2. Removes an always false conditional statement.
> 3. Removes duplicate OPAL_METHOD_LENGTH definition.
>
> These cleanup patches are submitted with the intend to submit a new feature
> after this.
>
> Changes from v2:
> 1. Added reviewed-bys
>
> Changes from v1:
> 1. Fixed up commit messages
>
> Revanth Rajashekar (3):
> block: sed-opal: Add/remove spaces
> block: sed-opal: Remove always false conditional statement
> block: sed-opal: Removed duplicate OPAL_METHOD_LENGTH definition
>
> block/opal_proto.h | 5 +----
> block/sed-opal.c | 49 ++++++++++++++++++++++++++++++++++++++--------
> 2 files changed, 42 insertions(+), 12 deletions(-)
Applied, adding a commit message for patch #3. Don't use empty commit
messages.
--
Jens Axboe
prev parent reply other threads:[~2019-08-20 15:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 15:30 [PATCH v3 0/3] block: sed-opal: Code Cleanup Patches Revanth Rajashekar
2019-08-20 15:30 ` [PATCH v3 1/3] block: sed-opal: Add/remove spaces Revanth Rajashekar
2019-08-20 15:30 ` [PATCH v3 2/3] block: sed-opal: Remove always false conditional statement Revanth Rajashekar
2019-08-20 15:30 ` [PATCH v3 3/3] block: sed-opal: Removed duplicate OPAL_METHOD_LENGTH definition Revanth Rajashekar
2019-08-20 15:35 ` Jens Axboe [this message]
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=2a4299af-2310-b34d-7129-90ab592976fe@kernel.dk \
--to=axboe@kernel.dk \
--cc=jonathan.derrick@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=revanth.rajashekar@intel.com \
--cc=sbauer@plzdonthack.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;
as well as URLs for NNTP newsgroup(s).