From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: Damien Le Moal <damien.lemoal@wdc.com>,
linux-block@vger.kernel.org, linux-scsi@vger.kernel.org,
"Martin K . Petersen" <martin.petersen@oracle.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] scsi: sd_zbc: Fix compilation warning
Date: Tue, 16 Jul 2019 10:34:23 -0400 [thread overview]
Message-ID: <yq1ftn6121c.fsf@oracle.com> (raw)
In-Reply-To: <f4812ac1-dfae-73d7-4722-4158c38d2382@kernel.dk> (Jens Axboe's message of "Tue, 16 Jul 2019 08:05:18 -0600")
Jens,
> Otherwise obviously looks fine to me. Martin, do you want to pick this
> one up?
Yep, I'll merge it.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2019-07-16 14:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 5:38 [PATCH] scsi: sd_zbc: Fix compilation warning Damien Le Moal
2019-07-16 14:05 ` Jens Axboe
2019-07-16 14:34 ` Martin K. Petersen [this message]
2019-07-17 1:24 ` Damien Le Moal
2019-07-17 1:27 ` 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=yq1ftn6121c.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=axboe@kernel.dk \
--cc=damien.lemoal@wdc.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/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).